Github user frodeso commented on the pull request:
https://github.com/apache/spark/pull/8252#issuecomment-136480957
@yhuai I've reported the issue
(https://issues.apache.org/jira/browse/SPARK-10377) . It has also been reported
to Datastax: https://datastax-oss.atlassian.net/browse/SPA
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8252#issuecomment-136420411
@frodeso Thank you for bringing this up. Can you open a JIRA for it and
attach the specific use-case at there (it will be code to also attach a link to
the place where Cas
Github user frodeso commented on the pull request:
https://github.com/apache/spark/pull/8252#issuecomment-135723748
This backport also includes the refactor of TakeOrdered to
TakeOrderedAndProject, which breaks code that refers to TakeOrdered. In a minor
version update that is perhaps
Github user yhuai closed the pull request at:
https://github.com/apache/spark/pull/8252
---
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 enabl
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8252#issuecomment-132069066
OK. Merged. 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 not
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8252#issuecomment-132068944
Thanks. I am merging it to branch 1.4.
---
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 cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/8252#issuecomment-132045195
LGTM. The change to optimizer is just refactor, so it's not necessary to
backport.
---
If your project is set up for it, you can reply to this email and have your
rep
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8252#issuecomment-131993817
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8252#issuecomment-131993819
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8252#issuecomment-131993723
[Test build #41052 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41052/consoleFull)
for PR 8252 at commit
[`5925ad4`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8252#issuecomment-131961750
[Test build #41052 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41052/consoleFull)
for PR 8252 at commit
[`5925ad4`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8252#issuecomment-131960531
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8252#issuecomment-131960510
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 h
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8252#issuecomment-131959714
@cloud-fan Can you take a look and make sure I am not missing any thing?
btw, I am intentionally not adding changes of `Optimizer` to this PR (looks
like those changes are
GitHub user yhuai opened a pull request:
https://github.com/apache/spark/pull/8252
[SPARK-7289] [SPARK-9949] [SQL] Backport SPARK-7289 and SPARK-9949 to
branch 1.4
The bug fixed by SPARK-7289 is a pretty serious one (Spark SQL generates
wrong results). We should backport the fix to
15 matches
Mail list logo
