Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/1190#discussion_r14114281
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/planning/patterns.scala
---
@@ -160,6 +160,43 @@ object HashFilteredJoin extends
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1189#issuecomment-46935816
Ok merging in master branch-1.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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/1189
---
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 ScrapCodes commented on a diff in the pull request:
https://github.com/apache/spark/pull/1179#discussion_r14115297
--- Diff: repl/src/main/scala/org/apache/spark/repl/SparkImports.scala ---
@@ -182,15 +182,26 @@ trait SparkImports {
// ambiguity errors will
Github user YanjieGao commented on the pull request:
https://github.com/apache/spark/pull/1134#issuecomment-46938049
Thanks a lot ,Chenghao . This code like a demo ,i think we could through
improve sample phrase and use some strategy to judge the which key set are
skew keys. we can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1190#issuecomment-46939722
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16049/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1190#issuecomment-46939721
Merged build finished. All automated tests passed.
---
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 rxin opened a pull request:
https://github.com/apache/spark/pull/1191
[SPARK-2253] Aggregator: Disable partial aggregation automatically when
reduction factor is low
TODOs
- [ ] Figure out the config option names
- [ ] Decide whether we want to create a new
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1152#issuecomment-46941044
@mateiz I submitted a patch to core's Aggregator in #1191.
After implementing it in Aggregator, I realized it might be hard for Spark
SQL to reuse Aggregator unless
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1191#issuecomment-46941091
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/1190#issuecomment-46941093
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/1190#issuecomment-46941097
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/1191#issuecomment-46941096
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 harishreedharan opened a pull request:
https://github.com/apache/spark/pull/1192
SPARK-1730. Make receiver store data reliably to avoid data-loss on
executor failures.
Added a new method in Receiver, ReceiverSupervisor, ReceiverSupervisorImpl
to store the data and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1191#issuecomment-46941163
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16050/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1191#issuecomment-46941162
Merged build finished.
---
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 harishreedharan closed the pull request at:
https://github.com/apache/spark/pull/1192
---
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 harishreedharan commented on the pull request:
https://github.com/apache/spark/pull/1192#issuecomment-46941330
Closing this as it includes commits already in another PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1191#issuecomment-46941462
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/1191#issuecomment-46941468
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 ueshin opened a pull request:
https://github.com/apache/spark/pull/1193
[SPARK-2254] [SQL] ScalaRefection should mark primitive types as
non-nullable.
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/1194
SPARK-2248: spark.default.parallelism does not apply in local mode
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark SPARK-2248
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1193#issuecomment-46941855
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/1194#issuecomment-46941852
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/1193#issuecomment-46941874
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 harishreedharan opened a pull request:
https://github.com/apache/spark/pull/1195
SPARK-1730. Make receiver store data reliably to avoid data-loss on exec...
...utor failures.
Added a new method in Receiver, ReceiverSupervisor, ReceiverSupervisorImpl
to store
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1194#issuecomment-46941873
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/1195#issuecomment-46942335
Can one of the admins verify this patch?
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1178#issuecomment-46942658
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1178#issuecomment-46942780
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/1178#issuecomment-46942791
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 ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/1176#issuecomment-46943415
Closing this for now, will work on this later.
---
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 ScrapCodes closed the pull request at:
https://github.com/apache/spark/pull/1176
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/772#issuecomment-46943576
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/772#issuecomment-46943584
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/772#issuecomment-46943923
Merged build finished.
---
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/772#issuecomment-46943925
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16056/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/772#issuecomment-46945776
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 ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/772#issuecomment-46945717
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/772#issuecomment-46945785
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/772#issuecomment-46945937
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16057/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/772#issuecomment-46945936
Merged build finished.
---
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/1191#issuecomment-46949381
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16052/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1190#issuecomment-46949376
Merged build finished.
---
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/1191#issuecomment-46949377
Merged build finished. All automated tests passed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1194#issuecomment-46949379
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16053/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1190#issuecomment-46949382
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16051/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1193#issuecomment-46950442
Merged build finished.
---
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/1178#issuecomment-46950441
Merged build finished.
---
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/1178#issuecomment-46950443
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16055/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1193#issuecomment-46950444
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16054/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/772#issuecomment-46954638
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/772#issuecomment-46954645
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/772#issuecomment-46956486
Merged build finished.
---
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/772#issuecomment-46956488
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16058/
---
If your project is set up for it, you can
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/772#issuecomment-46959692
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/772#issuecomment-46959931
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/772#issuecomment-46959941
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/772#issuecomment-46961449
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16059/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/772#issuecomment-46961448
Merged build finished.
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1178#issuecomment-46964631
Jenkins, test 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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1178#issuecomment-46964938
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/1178#issuecomment-46964949
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/1178#issuecomment-46969173
Merged build finished. All automated tests passed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1178#issuecomment-46969175
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16060/
---
If your
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/772#issuecomment-46971217
I am not sure what is causing this errros, tests run fine locally.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1178#issuecomment-46974602
@kayousterhout any other comments?
---
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 witgo commented on the pull request:
https://github.com/apache/spark/pull/772#issuecomment-46977329
It should be related to
[SPARK-1693](https://issues.apache.org/jira/browse/SPARK-1693)
---
If your project is set up for it, you can reply to this email and have your
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/1159#issuecomment-46979703
Jenkins, test 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 tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/900#discussion_r14132807
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -46,9 +46,14 @@ class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1159#issuecomment-46980261
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/1159#issuecomment-46980242
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/1159#issuecomment-46986709
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16061/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1159#issuecomment-46986706
Merged build finished. All automated tests passed.
---
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 vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1159#discussion_r14142240
--- Diff: docs/running-on-yarn.md ---
@@ -106,6 +106,13 @@ Most of the configs are the same for Spark on YARN as
for other deployment modes
set this
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1140#issuecomment-47007785
Jenkins, test 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/1140#issuecomment-47008248
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/1140#issuecomment-47008265
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/892
---
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 mateiz commented on the pull request:
https://github.com/apache/spark/pull/892#issuecomment-47013273
Thanks Rui. I've merged this in now.
---
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 kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/1178#issuecomment-47013887
This looks fine -- I still think the new error message is a little weird /
potentially misleading but fine to keep it if you feel strongly.
---
If your project is
Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/1178#issuecomment-47013969
(I tested this on the problem Shivaram and I originally ran into and this
works as intended)
---
If your project is set up for it, you can reply to this email and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1140#issuecomment-47014636
Merged build finished. All automated tests passed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1140#issuecomment-47014637
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16062/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1196#issuecomment-47014954
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1178#issuecomment-47014987
I don't feel strongly about my error message. What do you suggest it to be
instead?
---
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/1196#issuecomment-47014974
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 kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/1178#issuecomment-47015492
I preferred the old message that said launching the gateway process failed
-- but if you think that stdout interference is more common, then it's fine
to
GitHub user mattf opened a pull request:
https://github.com/apache/spark/pull/1197
[SPARK-2244] Fix hang introduced by SPARK-1466
The fix to SPARK-1466 (sha 38702487) opens a buffer for stderr, but
does not drain it under normal operation. The result is an eventual
hang
Github user mattf commented on the pull request:
https://github.com/apache/spark/pull/1178#issuecomment-47016309
oops, independently hit this
issue - https://issues.apache.org/jira/browse/SPARK-2244
patch - https://github.com/apache/spark/pull/1197
---
If your project is
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1197#issuecomment-47016354
Can one of the admins verify this patch?
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1178#issuecomment-47017888
Yeah, the problem is that stdout is not guaranteed to be an error message;
it could be a benign warning like the one #1050 is trying to fix. I'll make the
Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/1178#issuecomment-47018781
Sounds good @andrewor14
On Tue, Jun 24, 2014 at 12:17 PM, andrewor14 notificati...@github.com
wrote:
Yeah, the problem is that stdout is
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1178#issuecomment-47019905
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/1178#issuecomment-47019927
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/1196#issuecomment-47020392
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16063/
---
If your
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1178#issuecomment-47020450
@mattf The second issue is that this also masks stderr output to the
console, which contains important Spark logging information. Also, I tried your
patch out, and it
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1196#issuecomment-47020390
Merged build finished. All automated tests passed.
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1178#issuecomment-47020883
Here's the output of the latest commit in the event of stdout interference:
```
//... stack trace here
Exception: Launching GatewayServer failed! (Warning:
Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/1178#issuecomment-47021112
This looks perfect!
On Tue, Jun 24, 2014 at 12:44 PM, andrewor14 notificati...@github.com
wrote:
Here's the output of the latest commit
1 - 100 of 342 matches
Mail list logo
