Enable logical property propagation by default#22013
Enable logical property propagation by default#22013vivek-bharathan merged 1 commit intoprestodb:masterfrom
Conversation
d195678 to
eb95168
Compare
|
The only place in the docs that |
eb95168 to
3a74185
Compare
|
Codenotify: Notifying subscribers in CODENOTIFY files for diff 9dfc461...de6f59e.
|
...in/java/com/facebook/presto/sql/planner/iterative/rule/RemoveRedundantAggregateDistinct.java
Outdated
Show resolved
Hide resolved
|
I'm not sure we want to do this by default (unless the optimizations that use the property are off by default). We are not sure how they would affect our prod workloads. In any case, an installation can always turn it on cluster-wide using feature config. So I say keep it off for now. |
There was a problem hiding this comment.
Thanks! A few nits on formatting and punctuation.
You must add optimizer/logical-properties to https://github.com/prestodb/presto/blob/master/presto-docs/src/main/sphinx/optimizer.rst for the new page to be part of the left navbar.
Consider adding entries for exploit_constraints and optimizer.exploit-constraints to the Properties Reference doc, maybe in the Optimizer Properties topic.
If you're worried about that, can't you just disable it for your deployment and figure out a way (if any) to enable it gradually? |
Yeah - we were just talking about it. We will shut it off on our side. |
ZacBlanco
left a comment
There was a problem hiding this comment.
minor nit, otherwise lgtm
3a74185 to
e1a7d6f
Compare
steveburnett
left a comment
There was a problem hiding this comment.
Looks good! A couple of nits, nothing big.
e1a7d6f to
fe2fc03
Compare
fe2fc03 to
de6f59e
Compare
steveburnett
left a comment
There was a problem hiding this comment.
LGTM! (docs)
Pull updated branch, new local build.
|
@ClarenceThreepwood @tdcmeehan We found a correctness bug for the logical property propagation framework, a reproduce query is as follows: Returns 0 rows when the framework is on: Returns 1 row when the framework is off: Looking into the query plan, looks like that the framework incorrectly oversimplify the plan When framework is off: |
Fixes #21968