-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Revert "Enable logical property propagation by default" #22171
Conversation
This reverts commit 4b453a5.
Codenotify: Notifying subscribers in CODENOTIFY files for diff 88cda16...520f939.
|
@feilong-liu a bit late seeing this, but can you add the failing query as a test in ATQ so the regression doesn't get reintroduced? |
Add test mentioned in prestodb#22171 so as to avoid reintroducing the same problem.
@rschlussel Add in #22219 |
Add test mentioned in prestodb#22171 so as to avoid reintroducing the same problem.
Add test mentioned in #22171 so as to avoid reintroducing the same problem.
@feilong-liu - We would like to try enabling this again and want to minimize disruption. |
Add test mentioned in prestodb#22171 so as to avoid reintroducing the same problem.
Add test mentioned in prestodb#22171 so as to avoid reintroducing the same problem.
Reverts #22013
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 on:
When framework is off: