Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/8634#issuecomment-141561324
ping @liancheng does the updated version look OK to you?
---
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/8822#issuecomment-141561523
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8214#issuecomment-141561509
[Test build #42678 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42678/console)
for PR 8214 at commit
[`eac380b`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8214#issuecomment-141561568
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8806#issuecomment-141561504
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 this feature
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8822#issuecomment-141561521
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/8214#issuecomment-141561564
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8806#issuecomment-141561824
[Test build #1774 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1774/consoleFull)
for PR 8806 at commit
[`f0505de`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8214#issuecomment-141561748
[Test build #42685 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42685/consoleFull)
for PR 8214 at commit
[`41a10dd`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8826#issuecomment-141562010
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/4716#issuecomment-141562049
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/8806#issuecomment-141562019
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/4716#issuecomment-141562018
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8799#issuecomment-141562005
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8806#issuecomment-141562002
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8799#issuecomment-141562030
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/8826#issuecomment-141561995
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8799#issuecomment-141562534
[Test build #42688 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42688/consoleFull)
for PR 8799 at commit
[`a694ba2`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4716#issuecomment-141562859
[Test build #42689 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42689/consoleFull)
for PR 4716 at commit
[`ba71bfa`](https://gith
Github user holdenk commented on a diff in the pull request:
https://github.com/apache/spark/pull/8564#discussion_r39898676
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/LinearRegression.scala ---
@@ -298,11 +298,7 @@ class LinearRegressionModel private[ml] (
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8806#issuecomment-141562842
[Test build #42687 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42687/consoleFull)
for PR 8806 at commit
[`f0505de`](https://gith
Github user yhuai closed the pull request at:
https://github.com/apache/spark/pull/8702
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8826#issuecomment-141563507
[Test build #42686 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42686/consoleFull)
for PR 8826 at commit
[`cde37ff`](https://gith
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/8755#discussion_r39899010
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/basicOperators.scala
---
@@ -68,13 +68,47 @@ case class Generate(
g
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/8634#issuecomment-141563776
Merging to master.
---
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 f
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/8755#issuecomment-141563745
@cloud-fan I tried to change the output to be `Seq[String]` but failed,
because after resolve Generate, we still need to a Generate with Attribute.
---
If your project i
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/8634#issuecomment-141563704
@holdenk Sorry that I forgot to track this one... And yeah it LGTM now.
Thanks for fixing this!
---
If your project is set up for it, you can reply to this email and
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/8513#issuecomment-141564183
cc @Ishiihara who I think was maybe the original author of the fixed window
size.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8634
---
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 enab
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8812
---
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 enab
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/8828
[SPARK-10640] History server fails to parse TaskCommitDenied
... simply because the code is missing!
You can merge this pull request into a Git repository by running:
$ git pull https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8214#issuecomment-141566773
[Test build #42685 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42685/console)
for PR 8214 at commit
[`41a10dd`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8214#issuecomment-141566888
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/8214#issuecomment-141566891
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8800#issuecomment-141567397
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/8828#issuecomment-141567360
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8825#issuecomment-141567365
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8800#issuecomment-141567371
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141567383
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/8825#issuecomment-141567384
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8800#issuecomment-141567554
[Test build #42692 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42692/consoleFull)
for PR 8800 at commit
[`4746b82`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8749#issuecomment-141567614
[Test build #42674 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42674/console)
for PR 8749 at commit
[`eaf6169`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8749#issuecomment-141567737
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/8749#issuecomment-141567738
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8755#issuecomment-141567958
`generator.elementTypes` is used to stored the data types. We can create
new attributes based on the name and data types. Can we fix it by changing
`ResolveReferences` (ha
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8825#issuecomment-141567998
[Test build #42691 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42691/consoleFull)
for PR 8825 at commit
[`43eb0cf`](https://gith
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8825#discussion_r39900619
--- Diff: project/MimaExcludes.scala ---
@@ -70,6 +70,13 @@ object MimaExcludes {
"org.apache.spark.scheduler.AskPermissionToCommitOutput.this
GitHub user JoshRosen opened a pull request:
https://github.com/apache/spark/pull/8829
[SPARK-10708] [WIP] Consolidate sort shuffle implementations
There's a lot of duplication between SortShuffleManager and
UnsafeShuffleManager. Given that these now provide the same set of
functio
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141568727
[Test build #42690 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42690/consoleFull)
for PR 8828 at commit
[`f144147`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8564#issuecomment-141569056
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8829#issuecomment-141569048
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8829#issuecomment-141569068
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/8564#issuecomment-141569091
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 jaceklaskowski commented on the pull request:
https://github.com/apache/spark/pull/8795#issuecomment-141569374
So you want me to review the other documents for
no-backtick-code-formatted-in-table issue? I'm fine with it, but just need to
confirm my thinking.
---
If your
Github user tzachz commented on the pull request:
https://github.com/apache/spark/pull/8357#issuecomment-141569618
@yhuai I've just encountered this with my application, so I can give an
example of the conditions that cause this - here are some datapoints I hope
might help:
- My
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141570131
thanks, hadn't had a chance to finish this. I'll try out your changes on my
bad history file to make sure it works.
---
If your project is set up for it, you can repl
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8829#issuecomment-141570324
[Test build #42693 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42693/consoleFull)
for PR 8829 at commit
[`803f62f`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8564#issuecomment-141570505
[Test build #42694 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42694/consoleFull)
for PR 8564 at commit
[`d8baa47`](https://gith
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8827#issuecomment-141571421
also @davies
---
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 featu
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4716#issuecomment-141572238
[Test build #42689 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42689/console)
for PR 4716 at commit
[`ba71bfa`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4716#issuecomment-141572449
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4716#issuecomment-141572446
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/8795#issuecomment-141572755
Yeah I think that's worthwhile, as it should be fairly straightforward to
locate instances of this -- look for the areas where tables are used and skim
for backticks. At
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8826#issuecomment-141573315
[Test build #42686 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42686/console)
for PR 8826 at commit
[`cde37ff`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8826#issuecomment-141573477
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/8826#issuecomment-141573478
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8829#issuecomment-141574434
[Test build #42693 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42693/console)
for PR 8829 at commit
[`803f62f`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8829#issuecomment-141574477
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8829#issuecomment-141574481
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141575063
Great, thanks Tom.
---
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 andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/8781#discussion_r39903976
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/StreamingContextSuite.scala
---
@@ -180,6 +180,38 @@ class StreamingContextSuite extends Spa
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/8357#discussion_r39904017
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -37,7 +37,7 @@ import org.apache.spark.unsafe.types.CalendarInterval
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8357#issuecomment-141575633
@tzachz Thank you for the information! Those are super useful!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as w
GitHub user ericl opened a pull request:
https://github.com/apache/spark/pull/8830
[SPARK-9681] [ML] Support R feature interactions in RFormula
This integrates the Interaction feature transformer with the SparkR R
formula support (i.e. we support ':' now).
@mengxr
Yo
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8789#issuecomment-141575741
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 h
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8790#issuecomment-141575766
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8830#issuecomment-141576487
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8790#issuecomment-141576509
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/8789#issuecomment-141576498
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8789#issuecomment-141576519
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/8830#issuecomment-141576507
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/8790#issuecomment-141576495
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8789#issuecomment-141576853
[Test build #42697 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42697/consoleFull)
for PR 8789 at commit
[`62ec0f9`](https://gith
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/8561#issuecomment-141576888
@mengxr I reverted the SQL changes & the style issue with 1<<
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as w
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8790#issuecomment-141577158
[Test build #42696 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42696/consoleFull)
for PR 8790 at commit
[`dd615db`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8830#issuecomment-141577509
[Test build #42695 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42695/consoleFull)
for PR 8830 at commit
[`b16795a`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8564#issuecomment-141579035
[Test build #42694 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42694/console)
for PR 8564 at commit
[`d8baa47`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8564#issuecomment-141579393
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/8564#issuecomment-141579396
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/8781#discussion_r39905571
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/StreamingContextSuite.scala
---
@@ -180,6 +180,38 @@ class StreamingContextSuite extends SparkFunS
Github user SleepyThread commented on the pull request:
https://github.com/apache/spark/pull/4027#issuecomment-141579731
@andrewor14 @pwendell @tnachen @dragos. In my company we have patched the
Spark to specify minimum and maximum no of core per executor with only one
executor runnin
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/4027#issuecomment-141582708
The thought of this patch is give user the flexibility to provide a max and
min, and also optionally allow multiple executors or not. So in your case you
just need to sp
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8806#issuecomment-141582670
[Test build #1774 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1774/console)
for PR 8806 at commit
[`f0505de`](https://github
GitHub user JoshRosen opened a pull request:
https://github.com/apache/spark/pull/8831
[SPARK-10710] Remove ability to disable spilling in core and SQL
It does not make much sense to set `spark.shuffle.spill` or
`spark.sql.planner.externalSort` to false: I believe that these configu
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8831#issuecomment-141583145
/cc @rxin, @marmbrus, and @davies for review and sign-off.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as we
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8831#discussion_r39907246
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/execution/sort.scala
---
@@ -31,38 +31,12 @@ import org.apache.spark.{SparkEnv, InternalAccumulator,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8831#issuecomment-141583377
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/8831#issuecomment-141583355
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8799#issuecomment-141583625
[Test build #42688 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42688/console)
for PR 8799 at commit
[`a694ba2`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8799#issuecomment-141583698
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
401 - 500 of 618 matches
Mail list logo
