Github user viirya commented on the issue:
https://github.com/apache/spark/pull/18652
@gatorsmile Actually it is not rare we add a feature step by step in
SparkSQL. This is not a reason preventing us from adding this support. I think
this change already help much this kind of workload.
As said in previous discussion, we can't avoid few issues regarding the
non-deterministic non equi join condition. We can simply allow it, but it faces
inconsistency due to different join implementations. We can pull out it to
downstream project, but it possibly changes the number of calls.
`EnsureRequirements` can change the call order.
Notice that those issues are for non equi join condition, equi join
condition is free from the issues.
---
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
