rednaxelafx commented on PR #40488:

   Before the recent rounds of changes to EquivalentExpressions, the old 
`addExprTree` used to call `addExpr` in its core:
   That was still the case when `PhysicalAggregation` started using this 
mechanism to deduplicate expressions. I guess it started becoming "detached" 
from the main path when the recent refactoring happened that allows updating a 
separate equivalence map instead of the "main" one.
   Your proposed PR here further orphans that function from any actual use. 
Which is okay for keeping binary compatibility as much as possible.
   The inlined dedup logic in `PhysicalAggregation` looks rather ugly though. I 
don't have a strong opinion about that as long as other reviewers are okay. I'd 
prefer still retaining some sort of encapsulated collection for the dedup usage.
   BTW I updated my PR's test case because it makes more sense to check the 
return value from `addExpr` on the second invocation rather than on the first 
(both "not supported expression" and actual new expression cases would have 
gotten a `false` return value if we add that guard to the `addExpr()` function).

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail:

For queries about this service, please contact Infrastructure at:

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to