fix(physical-expr): Remove empty constants check when ordering is satisfied#14829
fix(physical-expr): Remove empty constants check when ordering is satisfied#14829xudong963 merged 2 commits intoapache:mainfrom
Conversation
|
cc @alamb Let me know if this change makes sense to you! |
berkaysynnada
left a comment
There was a problem hiding this comment.
Thank you @rkrishn7. I cannot really remember the need for that constants.is_empty() check. As the tests pass, probably it might be leftover. I was suspicious about the placeholder's equivalence information is set correctly. I checked it and see there is no problem with the union's inputs. So, it is LGTM
|
Thanks @alamb @berkaysynnada! Yeah, not too sure why it was there 🤔. For additional context, this also was occurring for The tests fixed here should cover this, but happy to add another test for |
|
Thanks all |
…isfied (apache#14829) * fix: Remove empty constants check when ordering is satisfied * fix: Update failing UNION [ALL] BY NAME SLTs
Which issue does this PR close?
Rationale for this change
This PR removes the condition that an inputs constants be empty in order to validate its ordering is satisfied by the target equivalence properties. If the ordering is satisfied, there should be no need to augment it with constants.
Across the failing tests, the lhs contained an ordering requirement while the right hand side did not. Thus, the ordering of the lhs should always satisfy the rhs properties. This was not the case however because both sides contained constants.
What changes are included in this PR?
Are these changes tested?
Failing tests have been updated
Are there any user-facing changes?
N/A