-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-54355][CONNECT] Make spark.connect.session.planCompression.defaultAlgorithm to support NONE
#53068
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
Conversation
…faultAlgorithm` to support `NONE`
|
Could you review this PR, please, @xi-db and @hvanhovell ? |
|
Could you review this when you have some time, @sryza ? |
|
Could you review this, @dtenedor ? |
|
Could you review this when you have some time, @cloud-fan ? |
|
Could you review this, @gengliangwang ? |
|
@dongjoon-hyun I’m not familiar with the related changes, so I’ll defer to other committers. |
|
No problem. Thank you for spending your time here, @gengliangwang . |
sarutak
left a comment
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 confirmed this works and NONE seems consistent with other similar configs.
|
Thank you so much, @sarutak . Merged to master/4.1 for Apache Spark 4.1.0 to provide a way to escape when we hit a regression . |
…faultAlgorithm` to support `NONE` ### What changes were proposed in this pull request? This PR aims to make `spark.connect.session.planCompression.defaultAlgorithm` to support `NONE` additionally. ### Why are the changes needed? **BEFORE** ``` $ bin/spark-connect-shell -c spark.connect.session.planCompression.defaultAlgorithm=NONE ... $ scala> spark.range(1).count() ... Caused by: org.apache.spark.SparkIllegalArgumentException: [INVALID_CONF_VALUE.OUT_OF_RANGE_OF_OPTIONS] The value 'NONE' in the config "spark.connect.session.planCompression.defaultAlgorithm" is invalid. It should be one of 'ZSTD'. SQLSTATE: 22022 ``` **AFTER** ``` $ bin/spark-connect-shell -c spark.connect.session.planCompression.defaultAlgorithm=NONE ... scala> spark.range(1).count() val res0: Long = 1 ``` ### Does this PR introduce _any_ user-facing change? No behavior change because this is a new option for a new feature. ### How was this patch tested? Pass the CIs. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #53068 from dongjoon-hyun/SPARK-54355. Authored-by: Dongjoon Hyun <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]> (cherry picked from commit e3e9863) Signed-off-by: Dongjoon Hyun <[email protected]>
|
Thanks @dongjoon-hyun for the PR! Late LGTM |
|
Thank you, @xi-db ! |
…faultAlgorithm` to support `NONE` ### What changes were proposed in this pull request? This PR aims to make `spark.connect.session.planCompression.defaultAlgorithm` to support `NONE` additionally. ### Why are the changes needed? **BEFORE** ``` $ bin/spark-connect-shell -c spark.connect.session.planCompression.defaultAlgorithm=NONE ... $ scala> spark.range(1).count() ... Caused by: org.apache.spark.SparkIllegalArgumentException: [INVALID_CONF_VALUE.OUT_OF_RANGE_OF_OPTIONS] The value 'NONE' in the config "spark.connect.session.planCompression.defaultAlgorithm" is invalid. It should be one of 'ZSTD'. SQLSTATE: 22022 ``` **AFTER** ``` $ bin/spark-connect-shell -c spark.connect.session.planCompression.defaultAlgorithm=NONE ... scala> spark.range(1).count() val res0: Long = 1 ``` ### Does this PR introduce _any_ user-facing change? No behavior change because this is a new option for a new feature. ### How was this patch tested? Pass the CIs. ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#53068 from dongjoon-hyun/SPARK-54355. Authored-by: Dongjoon Hyun <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
What changes were proposed in this pull request?
This PR aims to make
spark.connect.session.planCompression.defaultAlgorithmto supportNONEadditionally.Why are the changes needed?
BEFORE
AFTER
Does this PR introduce any user-facing change?
No behavior change because this is a new option for a new feature.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.