Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16785
**[Test build #72625 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72625/testReport)**
for PR 16785 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16785
since this change is related to SQL, cc @cloud-fan @hvanhovell
---
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
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16785
I don't find a way to improve `getAliasedConstraints` significantly by
re-writing its logic. The current way to improve its performance is using
parallel collection to do the transformation in
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16785
**[Test build #72625 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72625/testReport)**
for PR 16785 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16785
The rewritten logic is not correct. I am working to improve this with other
approach.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
