-
Notifications
You must be signed in to change notification settings - Fork 28.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SPARK-35811][PYTHON][FOLLOWUP] Deprecate DataFrame.to_spark_io #33631
Conversation
Test build #142022 has finished for PR 33631 at commit
|
retest this please |
Kubernetes integration test unable to build dist. exiting with code: 1 |
Test build #142023 has finished for PR 33631 at commit
|
Kubernetes integration test starting |
Merged to master and branch-3.2. |
### What changes were proposed in this pull request? This PR is followup for #32964, to improve the warning message. ### Why are the changes needed? To improve the warning message. ### Does this PR introduce _any_ user-facing change? The warning is changed from "Deprecated in 3.2, Use `spark.to_spark_io` instead." to "Deprecated in 3.2, Use `DataFrame.spark.to_spark_io` instead." ### How was this patch tested? Manually run `dev/lint-python` Closes #33631 from itholic/SPARK-35811-followup. Authored-by: itholic <haejoon.lee@databricks.com> Signed-off-by: Hyukjin Kwon <gurwls223@apache.org> (cherry picked from commit 3d72c20) Signed-off-by: Hyukjin Kwon <gurwls223@apache.org>
Kubernetes integration test status failure |
What changes were proposed in this pull request?
This PR is followup for #32964, to improve the warning message.
Why are the changes needed?
To improve the warning message.
Does this PR introduce any user-facing change?
The warning is changed from "Deprecated in 3.2, Use
spark.to_spark_io
instead." to "Deprecated in 3.2, UseDataFrame.spark.to_spark_io
instead."How was this patch tested?
Manually run
dev/lint-python