-
Notifications
You must be signed in to change notification settings - Fork 29.2k
[SPARK-28939][SQL][2.4] Propagate SQLConf for plans executed by toRdd #25734
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
Changes from 1 commit
e9d22e1
d145b14
43bd021
a5eb604
1b145e2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -7,6 +7,12 @@ displayTitle: Spark SQL Upgrading Guide | |
| * Table of contents | ||
| {:toc} | ||
|
|
||
| ## Upgrading from Spark SQL 2.4 to 2.4.5 | ||
|
|
||
| - Starting from 2.4.5, SQL configurations are effective also when a Dataset is converted to an RDD and its | ||
| plan is executed due to action on the derived RDD. The previous buggy behavior can be restored setting | ||
| `spark.sql.legacy.rdd.applyConf` to `false`. | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hi, @hvanhovell , @cloud-fan and @gatorsmile . As @mgaido91 asked here, this PR will add this flag only at For me, we don't need to add this configuration to
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't think we need to add the flag to master. We are allowed to break behavior there. |
||
|
|
||
| ## Upgrading from Spark SQL 2.4 to 2.4.1 | ||
|
|
||
| - The value of `spark.executor.heartbeatInterval`, when specified without units like "30" rather than "30s", was | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -1298,6 +1298,14 @@ object SQLConf { | |
| .booleanConf | ||
| .createWithDefault(true) | ||
|
|
||
| val USE_CONF_ON_RDD_OPERATION = | ||
| buildConf("spark.sql.legacy.rdd.applyConf") | ||
| .internal() | ||
| .doc("When false, SQL configurations are disregarded when operations on a RDD derived from" + | ||
| " a dataframe are executed. This is the (buggy) behavior up to 2.4.3.") | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||
| .booleanConf | ||
| .createWithDefault(true) | ||
|
|
||
| val REPLACE_EXCEPT_WITH_FILTER = buildConf("spark.sql.optimizer.replaceExceptWithFilter") | ||
| .internal() | ||
| .doc("When true, the apply function of the rule verifies whether the right node of the" + | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd personally refrain from using the term
buggy. Please explain what the previous behavior was.