Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3503#issuecomment-64865819
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23930/consoleFull)
for PR 3503 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3503#issuecomment-64865822
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/3504#issuecomment-64866336
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/3503#issuecomment-64866946
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/3503#issuecomment-64866937
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23931/consoleFull)
for PR 3503 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3504#issuecomment-64867758
[Test build #23933 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23933/consoleFull)
for PR 3504 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3504#issuecomment-64867766
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/3505#issuecomment-64868018
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/3505#issuecomment-64868013
[Test build #23932 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23932/consoleFull)
for PR 3505 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/3503#issuecomment-64868036
Thanks. Merging!
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/3475#issuecomment-64868218
Thanks. I'm merging this in master branch-1.2.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/3475
---
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/3496#issuecomment-64868793
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/154#issuecomment-64868760
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3496#issuecomment-64868789
[Test build #23934 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23934/consoleFull)
for PR 3496 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3506#issuecomment-64869963
[Test build #23936 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23936/consoleFull)
for PR 3506 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3506#issuecomment-64869966
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/3062#issuecomment-64870641
[Test build #23935 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23935/consoleFull)
for PR 3062 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3062#issuecomment-64870646
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/3507#issuecomment-64871175
ok to test
---
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/3507#issuecomment-64877532
[Test build #23937 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23937/consoleFull)
for PR 3507 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3507#issuecomment-64877541
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
GitHub user SaintBacchus opened a pull request:
https://github.com/apache/spark/pull/3508
[YARN][SPARK-3293]Fix yarn's web show SUCCEEDED when the driver throw a
exception in yarn-client
spark has five exit situations:
1.system.exit(0) - succeeds
2.clean exit main
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3508#issuecomment-64887757
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 SaintBacchus commented on the pull request:
https://github.com/apache/spark/pull/3508#issuecomment-64887880
The relevant PR is https://github.com/apache/spark/pull/2311 and
https://github.com/apache/spark/pull/2577
---
If your project is set up for it, you can reply to
Github user Liuchang0812 commented on the pull request:
https://github.com/apache/spark/pull/3428#issuecomment-64891677
This patch isn't very clear for reviewing, you moved a lot of codes. :+1:
---
If your project is set up for it, you can reply to this email and have your
reply
GitHub user SaintBacchus opened a pull request:
https://github.com/apache/spark/pull/3509
[Shuflle][SPARK-4641]file not found excepton in hash shuffle
It's very hard to replay this problem but actually I have meet this.
Assuming that, some hash key bucket have no elems in it and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3509#issuecomment-64892875
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 ryan-williams commented on a diff in the pull request:
https://github.com/apache/spark/pull/3467#discussion_r21033452
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/HistoryPage.scala ---
@@ -61,6 +72,15 @@ private[spark] class HistoryPage(parent:
GitHub user ravipesala opened a pull request:
https://github.com/apache/spark/pull/3510
[SPARK-4648][SQL] Support COALESCE function in Spark SQL and Hive QL
Currently HiveQL uses Hive UDF function for Coalesce. Usually using hive
udfs are memory intensive. Since Coalesce function
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3510#issuecomment-64901226
[Test build #23938 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23938/consoleFull)
for PR 3510 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3510#issuecomment-64904263
[Test build #23938 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23938/consoleFull)
for PR 3510 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3510#issuecomment-64904268
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/3456#issuecomment-64907251
Sorry I still don't see why this doesn't break sorting. Let's say I want to
answer which task as the longest GC time in this page? If there is pagination
there is now
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/3224#issuecomment-64907431
Jenkins, test this please. LGTM pending tests - this just pulls in clean-up
from upstream.
---
If your project is set up for it, you can reply to this email and have
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/3488#issuecomment-64907664
Have you seen any performance benefits from GZIP vs LZF on real workloads?
I don't think we should necessarily include a lot of codecs here because the
fragmentation
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3224#issuecomment-64907914
[Test build #23939 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23939/consoleFull)
for PR 3224 at commit
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/3509#issuecomment-64908608
Do you still see the issue after this patch?
https://github.com/apache/spark/commit/83b7a1c6503adce1826fc537b4db47e534da5cae
I believe that if there
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/3485#issuecomment-64910472
That's great that they updated the repo. Nonetheless I think we should put
this module behind a build flag for the reasons stated earlier. We can't be
dependent on a
Github user pwendell closed the pull request at:
https://github.com/apache/spark/pull/3485
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/3485#issuecomment-64911794
Actually even flagging only MQTT is complicated because of the examples. So
I'll just punt on this until later. It just leaves us in a situation where we
might have to
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/3506#issuecomment-64911921
Thanks Cheng - I'll pull this in.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/3506
---
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 tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/3484#discussion_r21039046
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMaster.scala
---
@@ -106,10 +106,14 @@ private[spark] class
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/3484#discussion_r21039238
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMaster.scala
---
@@ -403,42 +407,6 @@ private[spark] class
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/3484#discussion_r21039416
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMaster.scala
---
@@ -106,10 +106,14 @@ private[spark] class
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/3484#issuecomment-64914293
mostly looks good. I think we should fix the exit code before pulling it
in.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3224#issuecomment-64914989
[Test build #23939 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23939/consoleFull)
for PR 3224 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/3224
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/3451#issuecomment-64916243
Can you please close this issue?
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/1310#issuecomment-64916501
Let's close this issue
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/3504#issuecomment-64916632
Thanks - pulling this in.
---
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/3504
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/3490#issuecomment-64916925
Hi @lvsoft - it was not in the design of this component to support multiple
files, and I'd prefer not to do it. It makes it very hard to reason about the
effective
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/3480#issuecomment-64917713
Hey sean - any reason not to put these in `src/main/resources` within the
examples module? This is what spark sql does and it seems like a better model.
That location
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/3058#issuecomment-64917841
This LGTM - thanks for the fix.
---
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/3058
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/3405#issuecomment-64918092
@EntilZha are you building with Java 8? @srowen so did we decide this isn't
just an instance of #3058
---
If your project is set up for it, you can reply to this
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/3480#issuecomment-64918140
Generally yes I'd put resources in `src/main/resources`. These aren't in
that location, and the examples are written to expect them under `data/` at the
root level. I
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/3405#issuecomment-64918222
@pwendell There's a slightly different mystery here -- even if javadoc
warnings are generated, why are they an error in just this module? and why is
javadoc run at all
Github user EntilZha commented on the pull request:
https://github.com/apache/spark/pull/3405#issuecomment-64918891
@pwendell, I am building on Java 8.
---
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 tsudukim commented on the pull request:
https://github.com/apache/spark/pull/3456#issuecomment-64919851
I don't think it's a good idea that we lose the way to sort tasks globally
by other than launch time.
About OOM, I wrote something to the JIRA ticket.
---
If your
Github user tsudukim commented on the pull request:
https://github.com/apache/spark/pull/3467#issuecomment-64922238
@ryan-williams Thank you for your review!
I fixed them.
---
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/3467#issuecomment-64922504
[Test build #23941 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23941/consoleFull)
for PR 3467 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3510#issuecomment-64922900
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
GitHub user ravipesala opened a pull request:
https://github.com/apache/spark/pull/3511
[SPARK-4650][SQL] Supporting multi column support in countDistinct function
like count(distinct c1,c2..) in Spark SQL
Supporting multi column support in countDistinct function like
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/3275#issuecomment-64924585
Hey Matt - I commented on the JIRA.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3511#issuecomment-64924730
[Test build #23943 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23943/consoleFull)
for PR 3511 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3511#issuecomment-64924781
[Test build #23943 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23943/consoleFull)
for PR 3511 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3511#issuecomment-64924782
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user ravipesala commented on the pull request:
https://github.com/apache/spark/pull/3510#issuecomment-64925533
retest 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 this
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/3484#issuecomment-64925544
Okay I'd like to pull this in for rc1, so I'm going to merge this with the
edits that Tom suggested. Feel free to open up additional patches.
---
If your project is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3511#issuecomment-64925644
[Test build #23944 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23944/consoleFull)
for PR 3511 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/3484
---
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/3510#issuecomment-64926144
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/3510#issuecomment-64926143
[Test build #23942 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23942/consoleFull)
for PR 3510 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3467#issuecomment-64926902
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/3511#issuecomment-64928845
[Test build #23944 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23944/consoleFull)
for PR 3511 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3511#issuecomment-64928846
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/3428#discussion_r21044606
--- Diff: dev/merge_spark_pr.py ---
@@ -280,6 +275,13 @@ def get_version_json(version_str):
print Succesfully resolved %s with fixVersions=%s! %
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/3454
---
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 oza opened a pull request:
https://github.com/apache/spark/pull/3512
[SPARK-4651] Adding -Phadoop-2.5 and -Phadoop-2.6 to compile Spark with
newer versions of Hadoop
You can merge this pull request into a Git repository by running:
$ git pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3512#issuecomment-64936776
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/3512#issuecomment-64936804
This PR is messed up and needs to be rebased, at least, but see JIRA
comments.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user oza commented on the pull request:
https://github.com/apache/spark/pull/3512#issuecomment-64936933
@srowen Oh, my bad. I'm rebasing the 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 project
Github user oza commented on the pull request:
https://github.com/apache/spark/pull/3512#issuecomment-64937113
@srowen Updated. I ran Spark on YARN with Hadoop 2.5.2 by compiling this
option.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SaintBacchus closed the pull request at:
https://github.com/apache/spark/pull/3509
---
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
Github user hase1031 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3428#discussion_r21047410
--- Diff: dev/merge_spark_pr.py ---
@@ -280,6 +275,13 @@ def get_version_json(version_str):
print Succesfully resolved %s with fixVersions=%s! %
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/3195#issuecomment-64938212
OK @JoshRosen, I've added the backoff back in.
I didn't notice any regressions without the linear backoff, so I'll make a
note to remove it in a future version
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1082#issuecomment-64938215
This PR has gotten kind of stale, so do you mind closing this and
continuing any discussion / feature suggestions on JIRA? Thanks!
---
If your project is set up for
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3195#issuecomment-64938230
[Test build #23945 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23945/consoleFull)
for PR 3195 at commit
Github user DoingDone9 closed the pull request at:
https://github.com/apache/spark/pull/3491
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3207#issuecomment-64938337
This looks like a duplicate of another JIRA, which was resolved by #3259,
so do you mind closing this? Thanks!
(Sorry that I missed this PR; I guess it got
Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/3316#issuecomment-64938358
Have not encountered that history server cann't not be stopped. It is
always thrift server who is in that situation.
I commit this way because we use the
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3449#issuecomment-64938599
LGTM, so I'm going to merge this into `master` and the maintenance
branches. Thanks!
---
If your project is set up for it, you can reply to this email and have your
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/3449
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3410#issuecomment-64938699
This seem good to me; mind updating the PR title / description to say
footer instead of header
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3195#issuecomment-64939751
[Test build #23945 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23945/consoleFull)
for PR 3195 at commit
Github user oza commented on the pull request:
https://github.com/apache/spark/pull/3508#issuecomment-64941638
Please note that YARN-2091 changed the error code:
https://issues.apache.org/jira/browse/YARN-2091
---
If your project is set up for it, you can reply to this email and
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1310
---
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
1 - 100 of 103 matches
Mail list logo
