Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-154498875
Build started sha1 is merged.
---
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/9089#issuecomment-154498839
Build triggered. sha1 is merged.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-154499514
**[Test build #45232 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45232/consoleFull)**
for PR 9089 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-154528445
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45232/
---
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-154528444
Build finished. 5912 tests run, 0 skipped, 0 failed.
---
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/9089#issuecomment-154528236
**[Test build #45232 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45232/consoleFull)**
for PR 9089 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-148786929
@ankurdave Np, thanks for the fix. Btw, should the fix be accompanied by
a unit test to catch that issue?
---
If your project is set up for it, you can reply to
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-148181317
Calling uniqueKey on a DataFrame throws out the column names. Is that
intended?
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-148239326
[Test build #43757 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43757/consoleFull)
for PR 9089 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-148238867
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 ankurdave commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-148238916
@jkbradley Oops, thanks for catching that. I introduced it in
50717599f1eb5bf2184a6b1df2e0aebabdebddec because I misunderstood the function
of
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-148238883
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/9089#issuecomment-148266851
[Test build #43758 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43758/console)
for PR 9089 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-148267193
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/9089#issuecomment-148257737
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/9089#issuecomment-148257738
Test PASSed.
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/9089#issuecomment-148257662
[Test build #43757 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43757/console)
for PR 9089 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-148267196
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/9089#issuecomment-148240178
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/9089#issuecomment-148240194
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/9089#issuecomment-148241590
[Test build #43758 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43758/consoleFull)
for PR 9089 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147621974
[Test build #43620 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43620/console)
for PR 9089 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147622588
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/9089#issuecomment-147642587
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/9089#issuecomment-147642538
[Test build #43633 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43633/console)
for PR 9089 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147642585
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 ankurdave commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147636061
@rxin Thanks, I added the Experimental tags.
---
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 ankurdave commented on a diff in the pull request:
https://github.com/apache/spark/pull/9089#discussion_r41836429
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -362,14 +362,35 @@ class Analyzer(
j
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147627183
We can tag them as Experimental (even though the entire DataFrame API is
experimental!)
---
If your project is set up for it, you can reply to this email and have your
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/9089#discussion_r41833942
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -362,14 +362,35 @@ class Analyzer(
j
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147637636
[Test build #43633 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43633/consoleFull)
for PR 9089 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147643826
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/9089#issuecomment-147643952
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 ankurdave commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147625512
@marmbrus I addressed your comments from the review about a month ago:
1. Foreign key references now store the referenced relation directly as a
logical plan
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147642886
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147646844
[Test build #43638 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43638/consoleFull)
for PR 9089 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147622583
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/9089#issuecomment-147634492
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/9089#issuecomment-147634467
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/9089#issuecomment-147679090
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/9089#issuecomment-147678970
[Test build #43638 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43638/console)
for PR 9089 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147679091
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/9089#issuecomment-147600237
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/9089#issuecomment-147601410
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/9089#issuecomment-147600552
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/9089#issuecomment-147600546
[Test build #43619 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43619/console)
for PR 9089 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147600550
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 ankurdave opened a pull request:
https://github.com/apache/spark/pull/9089
[SPARK-11077] [SQL] Join elimination in Catalyst
Join elimination is a query optimization where certain joins can be
eliminated when followed by projections that only keep columns from one side
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147601433
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/9089#issuecomment-147601491
[Test build #43620 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43620/consoleFull)
for PR 9089 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147600249
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/9089#issuecomment-147600353
[Test build #43619 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43619/consoleFull)
for PR 9089 at commit
52 matches
Mail list logo
