Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13310#issuecomment-222006898
LGTM pending tests.
---
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 fea
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13310#issuecomment-222005824
**[Test build #59419 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59419/consoleFull)**
for PR 13310 at commit
[`89fac81`](https://gi
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1
---
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 ena
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1#issuecomment-222005224
Merging in master/2.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 have this
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/13276#issuecomment-222005115
```
2016-05-24 13:31:31.0 - stdout> spark-sql> ADD FILE
file:/home/jenkins/workspace/spark-master-test-maven-hadoop-
2016-05-24 13:31:31.004 - stdout>
2.7/s
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1#issuecomment-222004793
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1#issuecomment-222004790
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1#issuecomment-222004496
**[Test build #59411 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59411/consoleFull)**
for PR 1 at commit
[`e52fba9`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13332#issuecomment-222003043
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13332#issuecomment-222002844
**[Test build #59409 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59409/consoleFull)**
for PR 13332 at commit
[`454e6b6`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13332#issuecomment-222003041
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 projec
Github user aching commented on the pull request:
https://github.com/apache/spark/pull/13336#issuecomment-222001912
Thanks @sameeragarwal and @rxin!
---
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 no
Github user keypointt commented on the pull request:
https://github.com/apache/spark/pull/13308#issuecomment-222001350
Hi @srowen is there anything extra I should do?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If you
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/13310#discussion_r64823932
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SQLContext.scala ---
@@ -69,13 +67,30 @@ class SQLContext private[sql](
// Note: Since Spark 2.0 t
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13314
---
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 ena
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/13314#issuecomment-221999189
I'll also leave the JIRA open to remind us to check for remaining items.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/13314#issuecomment-221999100
Thanks! I'll merge this with master and branch-2.0 then.
---
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 hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/13315#issuecomment-221998770
LGTM
---
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
enabl
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13318#issuecomment-221998607
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13318#issuecomment-221998576
**[Test build #59418 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59418/consoleFull)**
for PR 13318 at commit
[`c72cdea`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13318#issuecomment-221998609
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user sureshthalamati commented on the pull request:
https://github.com/apache/spark/pull/13315#issuecomment-221998114
lgtm
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/13315#issuecomment-221997409
lgtm
---
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 an
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13318#issuecomment-221996288
**[Test build #59418 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59418/consoleFull)**
for PR 13318 at commit
[`c72cdea`](https://gi
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/13336#issuecomment-221995295
LGTM
---
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
enabl
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/13334#issuecomment-221994991
@techaddict you've misunderstood the JIRA. I removed them from
`HiveCompatibilitySuite` on purpose because they don't pass there. Instead you
should add them back to
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/13315#issuecomment-221994189
I tested partitioned data source tables too. If you add data back then the
partitions will be created again. I think that's OK.
---
If your project is set up for it
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13271#issuecomment-221993899
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13271#issuecomment-221993903
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/13107#issuecomment-221993686
@rxin After fixing those two, we still have some other limits (the number
of elements should be less than 512 mm), especially for on-heap mode. There are:
1) the larg
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/13275#issuecomment-221993639
To test a single subpackage, you can already use
```---modules='pyspark-ml'``` etc., so the ```---single-test``` arg may not be
necessary.
---
If your project is se
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13271#issuecomment-221993619
**[Test build #59403 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59403/consoleFull)**
for PR 13271 at commit
[`27328f9`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13318#issuecomment-221993456
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13318#issuecomment-221993459
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13318#issuecomment-221993227
**[Test build #59405 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59405/consoleFull)**
for PR 13318 at commit
[`f651956`](https://g
Github user sitalkedia commented on the pull request:
https://github.com/apache/spark/pull/13336#issuecomment-221991979
This is a nice find @sameeragarwal. Let me test this fix with our failing
job to see if that works.
---
If your project is set up for it, you can reply to this ema
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13107#issuecomment-221991347
Do we still need this pull request given the other two patches?
https://github.com/apache/spark/pull/13336
https://github.com/apache/spark/pull/13318
---
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/13336#issuecomment-221991388
LGTM
---
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 a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13315#issuecomment-221991110
**[Test build #59417 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59417/consoleFull)**
for PR 13315 at commit
[`e857027`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13336#issuecomment-221991081
**[Test build #59416 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59416/consoleFull)**
for PR 13336 at commit
[`f722e44`](https://gi
Github user sureshthalamati commented on the pull request:
https://github.com/apache/spark/pull/13315#issuecomment-221990818
@andrewor14 one minor thing I noticed when I looked at the table data
directories; In the case of regular tables truncate keeps the partition
directories, for
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13336#issuecomment-221990656
cc @tejasapatil this should fix one of the problems you guys run into.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Git
GitHub user sameeragarwal opened a pull request:
https://github.com/apache/spark/pull/13336
[SPARK-8428][SPARK-13850] Fix integer overflows in TimSort
## What changes were proposed in this pull request?
This patch fixes a few integer overflows in
`UnsafeSortDataFormat.copyR
Github user sameeragarwal commented on the pull request:
https://github.com/apache/spark/pull/13336#issuecomment-221990354
cc @davies @rxin
---
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 th
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1#issuecomment-221990349
LGTM pending tests.
---
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 fea
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13335#issuecomment-221988548
**[Test build #59415 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59415/consoleFull)**
for PR 13335 at commit
[`4f7ee7f`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13316#issuecomment-221988230
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13316#issuecomment-221988228
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12938#issuecomment-221988093
**[Test build #59408 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59408/consoleFull)**
for PR 12938 at commit
[`53ab790`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12938#issuecomment-221988239
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12938#issuecomment-221988241
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13316#issuecomment-221987929
**[Test build #59398 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59398/consoleFull)**
for PR 13316 at commit
[`325a2ea`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12824#issuecomment-221987759
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12824#issuecomment-221987762
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12824#issuecomment-221987455
**[Test build #59397 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59397/consoleFull)**
for PR 12824 at commit
[`1c48d07`](https://g
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/13335
[SPARK-15580][SQL]Add ContinuousQueryInfo to make ContinuousQueryListener
events serializable
## What changes were proposed in this pull request?
This PR adds ContinuousQueryInfo to make C
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13331#issuecomment-221987281
**[Test build #59414 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59414/consoleFull)**
for PR 13331 at commit
[`d688034`](https://gi
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/13331#discussion_r64816282
--- Diff: sql/core/src/test/scala/org/apache/spark/sql/DatasetSuite.scala
---
@@ -436,20 +435,6 @@ class DatasetSuite extends QueryTest with
SharedSQLCont
Github user xinhhuynh commented on a diff in the pull request:
https://github.com/apache/spark/pull/13330#discussion_r64816159
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala ---
@@ -1665,7 +1665,7 @@ class Dataset[T] private[sql](
}
/**
Github user sitalkedia commented on the pull request:
https://github.com/apache/spark/pull/13318#issuecomment-221986302
Thank you for making this 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 d
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13271#issuecomment-221986043
**[Test build #59413 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59413/consoleFull)**
for PR 13271 at commit
[`d912d62`](https://gi
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/13331#discussion_r64815745
--- Diff: sql/core/src/test/scala/org/apache/spark/sql/DatasetSuite.scala
---
@@ -440,14 +439,16 @@ class DatasetSuite extends QueryTest with
SharedSQLCon
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1#issuecomment-221985662
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1#issuecomment-221985660
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1#issuecomment-221985330
**[Test build #59400 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59400/consoleFull)**
for PR 1 at commit
[`5a71f89`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13334#issuecomment-221985148
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 projec
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/13283#discussion_r64815365
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -448,6 +448,14 @@ class Analyzer(
}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13334#issuecomment-221985150
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13334#issuecomment-221984940
**[Test build #59407 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59407/consoleFull)**
for PR 13334 at commit
[`6361ac5`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13315#issuecomment-221984931
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13315#issuecomment-221984936
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13315#issuecomment-221984586
**[Test build #59401 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59401/consoleFull)**
for PR 13315 at commit
[`d994460`](https://g
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/13283#discussion_r64814173
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -448,6 +448,14 @@ class Analyzer(
}
Github user kayousterhout commented on a diff in the pull request:
https://github.com/apache/spark/pull/11996#discussion_r64814037
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/TaskSetManagerSuite.scala ---
@@ -795,6 +795,7 @@ class TaskSetManagerSuite extends SparkFunSu
Github user kayousterhout commented on a diff in the pull request:
https://github.com/apache/spark/pull/11996#discussion_r64813822
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala ---
@@ -64,6 +64,8 @@ private[spark] class TaskSchedulerImpl(
/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11996#issuecomment-221982283
**[Test build #59412 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59412/consoleFull)**
for PR 11996 at commit
[`b05908c`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1#issuecomment-221982305
**[Test build #59411 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59411/consoleFull)**
for PR 1 at commit
[`e52fba9`](https://gi
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/13280#issuecomment-221982103
I think we should upgrade Parquet to 1.8.1 in Spark 2.0 due to the
following reasons:
1. Get PARQUET-251 fixed so that we no longer write corrupted statistics
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13139#issuecomment-221981860
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13139#issuecomment-221981865
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13139#issuecomment-221981828
**[Test build #59410 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59410/consoleFull)**
for PR 13139 at commit
[`6e7ddd3`](https://g
Github user clockfly commented on a diff in the pull request:
https://github.com/apache/spark/pull/1#discussion_r64812858
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -1795,7 +1795,9 @@ class Analyzer(
def apply(pl
Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/11996#issuecomment-221981351
Looks like there are build errors, where you need to update makeProgressBar
in
streaming/src/main/scala/org/apache/spark/streaming/ui/AllBatchesTable.scala:95
an
Github user sureshthalamati commented on the pull request:
https://github.com/apache/spark/pull/13315#issuecomment-221980355
@andrewor14 After I cleaned up the old metastore_db , truncate worked as
expected. Thanks
---
If your project is set up for it, you can reply to this email
Github user xwu0226 commented on a diff in the pull request:
https://github.com/apache/spark/pull/13088#discussion_r64812164
--- Diff: conf/spark-defaults.conf.template ---
@@ -25,3 +25,4 @@
# spark.serializer
org.apache.spark.serializer.KryoSerializer
# s
Github user xwu0226 commented on a diff in the pull request:
https://github.com/apache/spark/pull/13088#discussion_r64812131
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SparkSession.scala
---
@@ -585,6 +585,18 @@ class SparkSession private(
sparkContext.stop()
Github user sethah commented on a diff in the pull request:
https://github.com/apache/spark/pull/13139#discussion_r64811972
--- Diff: docs/ml-classification-regression.md ---
@@ -374,6 +374,137 @@ regression model and extracting model summary
statistics.
+## G
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13139#issuecomment-221979783
**[Test build #59410 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59410/consoleFull)**
for PR 13139 at commit
[`6e7ddd3`](https://gi
Github user xwu0226 commented on a diff in the pull request:
https://github.com/apache/spark/pull/13088#discussion_r64811898
--- Diff:
repl/scala-2.11/src/main/scala/org/apache/spark/repl/SparkILoop.scala ---
@@ -43,6 +43,10 @@ class SparkILoop(in0: Option[BufferedReader], out:
JP
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13332#issuecomment-221979812
**[Test build #59409 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59409/consoleFull)**
for PR 13332 at commit
[`454e6b6`](https://gi
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/13332#issuecomment-221979513
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 th
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/13332#issuecomment-221979499
Jenkins add to whitelist
---
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 th
Github user xwu0226 commented on a diff in the pull request:
https://github.com/apache/spark/pull/13088#discussion_r64811522
--- Diff: repl/scala-2.11/src/main/scala/org/apache/spark/repl/Main.scala
---
@@ -88,10 +88,22 @@ object Main extends Logging {
}
val
Github user xwu0226 commented on a diff in the pull request:
https://github.com/apache/spark/pull/13088#discussion_r64811442
--- Diff: repl/scala-2.11/src/main/scala/org/apache/spark/repl/Main.scala
---
@@ -88,10 +88,22 @@ object Main extends Logging {
}
val
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/13329#issuecomment-221979133
Some of this is OK, some of it isn't an improvement. I don't think we
should just change a few instances of format to interpolation, nor do I think
it is necessarily wor
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13319
---
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 ena
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/13319#issuecomment-221978572
m2.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 have this feature
enabl
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1#discussion_r64810777
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -1795,7 +1795,9 @@ class Analyzer(
def apply(plan:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12938#issuecomment-221974702
**[Test build #59408 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59408/consoleFull)**
for PR 12938 at commit
[`53ab790`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13329#issuecomment-221974373
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 projec
401 - 500 of 893 matches
Mail list logo
