-
Notifications
You must be signed in to change notification settings - Fork 439
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
[GLUTEN-6920][CORE] Redesign and move trait GlutenPlan
to gluten-core
#8036
base: main
Are you sure you want to change the base?
Conversation
Run Gluten Clickhouse CI on x86 |
GlutenPlan
to gluten-core
Run Gluten Clickhouse CI on x86 |
2 similar comments
Run Gluten Clickhouse CI on x86 |
Run Gluten Clickhouse CI on x86 |
0c598a4
to
cbcc5eb
Compare
Run Gluten Clickhouse CI on x86 |
Run Gluten Clickhouse CI on x86 |
8 similar comments
Run Gluten Clickhouse CI on x86 |
Run Gluten Clickhouse CI on x86 |
Run Gluten Clickhouse CI on x86 |
Run Gluten Clickhouse CI on x86 |
Run Gluten Clickhouse CI on x86 |
Run Gluten Clickhouse CI on x86 |
Run Gluten Clickhouse CI on x86 |
Run Gluten Clickhouse CI on x86 |
Run Gluten Clickhouse CI on x86 |
328d94c
to
b87bf02
Compare
Run Gluten Clickhouse CI on x86 |
Run Gluten Clickhouse CI on x86 |
Run Gluten Clickhouse CI on x86 |
1 similar comment
Run Gluten Clickhouse CI on x86 |
Run Gluten Clickhouse CI on x86 |
Run Gluten Clickhouse CI on x86 |
Run Gluten Clickhouse CI on x86 |
Run Gluten Clickhouse CI on x86 |
GlutenPlan
to gluten-core
GlutenPlan
to gluten-core
Part of #6920
This work factors out
GlutenPlan
to separate the APIs to 2 places:doValidate
, move to new APIValidatablePlan
andTransformSupport
GlutenPlan
After the change,
GlutenPlan
will become a thin and base interface for query plans of all Gluten backends. APIs inGlutenPlan
will be used by query planner to decide whether pre-transition or post-transition is needed for this plan node. Backends could still define their own validation logic if needed, by extending the trait by themselves.GlutenPlan
will hidesupportsColumnar
andsupportsRowBased
(for Spark version > 3.2) up and expose Gluten APIsrowType
andbatchType
to sub-classes instead. The later two are more flexible since Gluten's query planner could distinguish between different batch types and add essential transitions among them and vanilla rows.