Github user viirya commented on the issue:
https://github.com/apache/spark/pull/15146
@hvanhovell @cloud-fan Thanks!
---
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
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/15146
Merging to master. Thanks!
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15146
Merged build finished. Test PASSed.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15146
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65630/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15146
**[Test build #65630 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65630/consoleFull)**
for PR 15146 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15146
**[Test build #65630 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65630/consoleFull)**
for PR 15146 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/15146
I guess if using the same analyzed plan increases the chance to reuse
exchange, then it may improve the performance. Anyway, it is not the purpose of
this change. Because the analyzed subquery plan
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/15146
@hvanhovell This is for analyzer change and adds CTE in CTE feature. I
don't expect there is performance improvement.
---
If your project is set up for it, you can reply to this email and have your
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/15146
@viirya does this improve performance?
---
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
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15146
Seems good, but not quite sure, cc @hvanhovell to confirm
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15146
Merged build finished. Test PASSed.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15146
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65588/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15146
**[Test build #65588 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65588/consoleFull)**
for PR 15146 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15146
Merged build finished. Test PASSed.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15146
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65586/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15146
**[Test build #65586 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65586/consoleFull)**
for PR 15146 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/15146
cc @hvanhovell @cloud-fan
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15146
**[Test build #65588 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65588/consoleFull)**
for PR 15146 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15146
**[Test build #65586 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65586/consoleFull)**
for PR 15146 at commit
19 matches
Mail list logo
