Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/14111
@lianhuiwang, after taking a look at this example, I think this is a very
special case: 2 physical plans reference to one same subquery(same instance).
However, I don't think this is a valid case, I'd rather treat it as a bug of
constraints propagation. Except this case, do we have another case that the
simpler approach can't handle?
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
