-
Notifications
You must be signed in to change notification settings - Fork 463
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
[VL] RAS: Avoid adding R2C whose schema contains complex data types #7229
Conversation
Run Gluten Clickhouse CI |
Run Gluten Clickhouse CI |
1 similar comment
Run Gluten Clickhouse CI |
Run Gluten Clickhouse CI |
case r2c: RowToColumnarExecBase if hasComplexTypes(r2c.schema) => | ||
// Avoid moving computation back to native when transition has complex types in schema. | ||
// Such transitions are observed to be extreme expensive as of now. | ||
Long.MaxValue |
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.
Can we add a more reasonable value to the cost? How can we measure the operator cost now?
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.
We can use it as a temp solution. The r2c is very expensive.
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.
Yes. it's just a heuristic as a temp solution from query optimizer side.
Run Gluten Clickhouse CI |
Run Gluten Clickhouse CI |
Run Gluten Clickhouse CI |
temp fix of #7223 |
It's observed Velox R2C becomes expensive when containing complex data types as input. Add a coster in rough cost model to address the issue.
To enable rough cost model: