Github user sameeragarwal commented on the issue:
https://github.com/apache/spark/pull/16998
@viirya please correct me if I'm wrong but scanning through this patch, it
appears that the underlying problem is that duplicating and tracking aliased
constraints using a `Set` tends to blow up quickly (causing regressions) and
this patch is proposing an alternate data structure
(`aliasedExpressionsInConstraints`) to keep track of aliases? For e.g., in your
example where `a > b`, and `a` is aliased to `c` and `d`, we currently track
constraints as `Set(a > b, c > b, d > b)` whereas you'd like it to be tracked
as `Set(a > b)` and `Map(a, Set(c, d))`? Is that correct?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
