Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17670
Thanks! Merging to master/2.2
---
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
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/17670
ping
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17670
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/17670
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75975/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17670
**[Test build #75975 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75975/testReport)**
for PR 17670 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17670
**[Test build #75975 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75975/testReport)**
for PR 17670 at commit
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/17670
Jenkins, retest this please.
---
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/17670
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/17670
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75971/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17670
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/17670
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75974/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17670
**[Test build #75974 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75974/testReport)**
for PR 17670 at commit
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/17670
better to open another pr to backport to v2.2?
---
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
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17670
LGTM except a comment.
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17670
Ok, I am fine to keep the existing way.
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17670
**[Test build #75971 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75971/testReport)**
for PR 17670 at commit
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/17670
Looking around the related code, I think we cannot easily set
`defaultParallelism` inside `catalyst.plans.logical` because there is no
obvious way to access `SQLContext` there. So, IIUC, we cannot
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/17670
okay, I'll fix soon. 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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17670
As @jaceklaskowski said, it would be good to fill `numSlices` in the rule
`ResolveTableValuedFunctions`, if it is None.
---
If your project is set up for it, you can reply to this email and
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/17670
@gatorsmile WDYT?
---
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
Github user jaceklaskowski commented on the issue:
https://github.com/apache/spark/pull/17670
I think the change should rather be [here](ResolveTableValuedFunctions)
where the built-in table-valued function `range` is resolved.
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17670
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/17670
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75900/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17670
**[Test build #75900 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75900/testReport)**
for PR 17670 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17670
**[Test build #75900 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75900/testReport)**
for PR 17670 at commit
25 matches
Mail list logo
