Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221462008
Thank you, @rxin !
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13282
---
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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221453145
LGTM - merging in master/2.0.
---
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 pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221452569
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221452568
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221452428
**[Test build #59240 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59240/consoleFull)**
for PR 13282 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221447277
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221447276
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221447119
**[Test build #59234 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59234/consoleFull)**
for PR 13282 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221437547
**[Test build #59240 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59240/consoleFull)**
for PR 13282 at commit
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221437321
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221436608
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221436586
**[Test build #59237 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59237/consoleFull)**
for PR 13282 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221436606
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221435093
**[Test build #59223 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59223/consoleFull)**
for PR 13282 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221435298
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221435340
**[Test build #59237 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59237/consoleFull)**
for PR 13282 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221435299
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221435072
It seems not necessary since this PR prevents at the level of `Repartition`
ctor.
```
case class Repartition(numPartitions: Int, shuffle: Boolean, child:
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221431790
CheckAnalysis?
---
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 pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221431220
**[Test build #59234 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59234/consoleFull)**
for PR 13282 at commit
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221431064
Hi, @rxin .
I added that to catalyst/DataSetSuite/DataFrameSuite, too.
So far, I cannot find a proper place in Analyzer. If you mind, could you
give me
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221426314
Yes. They need this. I'll add that.
---
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
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221425046
Thank you for review, @rxin .
I'll check them whether they need this.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221424583
Can we add these to the dataframe API? And in the analyzer?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221414021
**[Test build #59223 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59223/consoleFull)**
for PR 13282 at commit
GitHub user dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/13282
[SPARK-15512][CORE] repartition(0) should raise IllegalArgumentException
## What changes were proposed in this pull request?
Previously, SPARK-8893 added the constraints on positive
27 matches
Mail list logo
