Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-127023732
ok, I am closing this pr.
---
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 chenghao-intel closed the pull request at:
https://github.com/apache/spark/pull/6413
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-126941728
If I'm not mistaken, I think that this patch's changes will be subsumed by
the combination of #7773 and the null-unsafe/safe parts of #7685. Are there
any changes in
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-126943117
@JoshRosen Right, #7773 and the null-unsafe/safe parts of #7685 will
address the issue.
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-121072452
Build triggered.
---
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 liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/6413#discussion_r33999240
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/physical/partitioning.scala
---
@@ -76,144 +72,267 @@ case class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-118348858
[Test build #36499 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36499/consoleFull)
for PR 6413 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-118368276
[Test build #36499 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36499/console)
for PR 6413 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-118368479
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-118347540
Merged build triggered.
---
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/6413#issuecomment-118347630
Merged build started.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-117950030
[Test build #36368 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36368/consoleFull)
for PR 6413 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-117949791
Merged build triggered.
---
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/6413#issuecomment-117949834
Merged build started.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-117950716
[Test build #36368 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36368/console)
for PR 6413 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-117950720
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-117962146
Merged build started.
---
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/6413#issuecomment-117962126
Merged build triggered.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-117962224
[Test build #36379 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36379/consoleFull)
for PR 6413 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-117993189
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/6413#issuecomment-117993157
[Test build #36379 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36379/console)
for PR 6413 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-118026004
[Test build #36392 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36392/consoleFull)
for PR 6413 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-118025333
Merged build started.
---
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/6413#issuecomment-118007781
Merged build triggered.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-118051348
[Test build #36392 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36392/console)
for PR 6413 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-118051389
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 chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-117202219
Sorry, I found another bug, will solve it soon.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-116591217
[Test build #35975 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35975/consoleFull)
for PR 6413 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-116628777
[Test build #35975 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35975/console)
for PR 6413 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-116628800
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-116590949
Merged build started.
---
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 chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-116511523
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/6413#issuecomment-116512079
Merged build triggered.
---
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/6413#issuecomment-116505194
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/6413#issuecomment-116505107
[Test build #35961 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35961/console)
for PR 6413 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-116506759
[Test build #35965 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35965/console)
for PR 6413 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-116506833
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 chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-116884814
@yhuai sorry it's a big change. :) can you review this for me?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
38 matches
Mail list logo
