-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-19944][SQL] Move SQLConf from sql/core to sql/catalyst #17285
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
|
Test build #74484 has finished for PR 17285 at commit
|
|
Test build #74485 has finished for PR 17285 at commit
|
| * for ticket SPARK-19944 (moves SQLConf from sql/core to sql/catalyst). This class should | ||
| * eventually be removed (test cases should just create SQLConf and set values appropriately). | ||
| */ | ||
| case class SimpleCatalystConf( |
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.
Does SQLConf contain these defaults?
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.
it does.
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 think this is just to keep the code change minimal.
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.
Yeah, I figured as much.
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.
Yup the purpose is to minimize the change. Otherwise I will change 50+ files ...
| .internal() | ||
| .stringConf | ||
| .createWithDefault(classOf[ParquetOutputCommitter].getName) | ||
| .createWithDefault("org.apache.parquet.hadoop.ParquetOutputCommitter") |
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.
It is a bit weird to me that we refer to sql/core configs in catalyst. Shouldn't we just move the dynamic configuration and the catalyst only configurations to CatalystConf and make SQLConf extend this?
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.
yea good idea
|
LGTM, merging to master. We should have a follow-up PR to further clean up the code and address some comments. |
|
A late LGTM |
This patch moves SQLConf from sql/core to sql/catalyst. To minimize the changes, the patch used type alias to still keep CatalystConf (as a type alias) and SimpleCatalystConf (as a concrete class that extends SQLConf). Motivation for the change is that it is pretty weird to have SQLConf only in sql/core and then we have to duplicate config options that impact optimizer/analyzer in sql/catalyst using CatalystConf. N/A Author: Reynold Xin <[email protected]> Closes apache#17285 from rxin/SPARK-19944.
## What changes were proposed in this pull request? This is a follow-up of apache#17285 . ## How was this patch tested? existing tests Author: Wenchen Fan <[email protected]> Closes apache#17521 from cloud-fan/conf.
What changes were proposed in this pull request?
This patch moves SQLConf from sql/core to sql/catalyst. To minimize the changes, the patch used type alias to still keep CatalystConf (as a type alias) and SimpleCatalystConf (as a concrete class that extends SQLConf).
Motivation for the change is that it is pretty weird to have SQLConf only in sql/core and then we have to duplicate config options that impact optimizer/analyzer in sql/catalyst using CatalystConf.
How was this patch tested?
N/A