Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16998
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73316/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16998
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/16998
**[Test build #73316 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73316/testReport)**
for PR 16998 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16998
**[Test build #73316 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73316/testReport)**
for PR 16998 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16998
@sameeragarwal That's correct.
> By the way, as an aside we should probably allow constraint
inference/propagation to be turned off via a conf flag to provide a quick work
around against
Github user sameeragarwal commented on the issue:
https://github.com/apache/spark/pull/16998
By the way, as an aside we should probably allow constraint
inference/propagation to be turned off via a conf flag to provide a quick work
around against these kind of problems.
---
If your
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
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16998
> I do not get your points. What does this mean? Constraint propagation is
a bottom up mechanism for inferring the constraints. Can you elaborate your
idea in the more formal way.
We fully
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16998
> Another issue is we actually don't need the additional constraints at
most of time. For example, if there is a constraint "a > b", and "a" is aliased
to "c" and "d". When we use this
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16998
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/16998
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73174/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16998
**[Test build #73174 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73174/testReport)**
for PR 16998 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16998
**[Test build #73174 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73174/testReport)**
for PR 16998 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16998
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73163/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16998
Merged build finished. Test FAILed.
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/16998
**[Test build #73163 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73163/testReport)**
for PR 16998 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16998
**[Test build #73163 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73163/testReport)**
for PR 16998 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16998
**[Test build #73158 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73158/testReport)**
for PR 16998 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16998
@hvanhovell Yes. #16785 only does a limited improvement. Both #16785 and
this are non-parallel approach.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16998
Merged build finished. Test FAILed.
---
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/16998
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73159/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16998
**[Test build #73159 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73159/testReport)**
for PR 16998 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16998
**[Test build #73159 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73159/testReport)**
for PR 16998 at commit
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/16998
@viirya does this PR supersede #16785? I do like the non-parallel approach.
I will try to take a more in-depth look at the end of the week (beginning of
the next sprint).
---
If your project
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16998
**[Test build #73158 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73158/testReport)**
for PR 16998 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16998
cc @cloud-fan @hvanhovell @sameeragarwal
---
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
26 matches
Mail list logo
