Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7079#issuecomment-116490709
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7078#issuecomment-116491120
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7079#issuecomment-116490658
[Test build #35967 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35967/console)
for PR 7079 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6394#issuecomment-116490921
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/6394#issuecomment-116490841
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7078#issuecomment-116491072
[Test build #35968 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35968/console)
for PR 7078 at commit
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/6971#discussion_r33439534
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/misc.scala
---
@@ -47,4 +48,44 @@ case class Md5(child: Expression)
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7079
---
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/6976#issuecomment-116506412
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-116506759
[Test build #35965 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35965/console)
for PR 6413 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6976#issuecomment-116506468
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/6413#issuecomment-116506833
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/7081
[SPARK-8701][Streaming][WebUI] Add input metadata in the batch page
This PR adds `metadata` to `InputInfo`. `InputDStream` can report its
metadata for a batch and it will be shown in the batch
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/7055#issuecomment-116541865
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/7053#issuecomment-116541975
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/6737#issuecomment-116467424
[Test build #35964 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35964/consoleFull)
for PR 6737 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-116475434
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6394#issuecomment-116492491
[Test build #35971 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35971/consoleFull)
for PR 6394 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6982#issuecomment-116510065
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/6982#issuecomment-116510108
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/6737#issuecomment-116465306
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/6737#issuecomment-116465396
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 qiansl127 commented on a diff in the pull request:
https://github.com/apache/spark/pull/6971#discussion_r33437963
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/misc.scala
---
@@ -47,4 +48,44 @@ case class Md5(child: Expression)
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/6976#discussion_r33437986
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/math.scala
---
@@ -287,6 +286,85 @@ case class Pow(left: Expression, right:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6394#issuecomment-116484564
[Test build #35970 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35970/consoleFull)
for PR 6394 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7078#issuecomment-116487440
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7078#issuecomment-116487415
[Test build #35966 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35966/console)
for PR 7078 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6976#issuecomment-116507385
[Test build #35972 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35972/consoleFull)
for PR 6976 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/7060#discussion_r33440758
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/stat/StatFunctions.scala
---
@@ -119,14 +119,14 @@ private[sql] object StatFunctions extends
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/7060#discussion_r33440738
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/stat/StatFunctions.scala
---
@@ -119,14 +119,14 @@ private[sql] object StatFunctions extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6982#issuecomment-116511277
[Test build #35974 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35974/consoleFull)
for PR 6982 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7080#issuecomment-116515950
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/7081#issuecomment-116520290
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 davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/6982#discussion_r33436295
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/ExtractValue.scala
---
@@ -195,6 +205,11 @@ case class GetArrayItem(child:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6963#issuecomment-116461371
[Test build #975 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/975/consoleFull)
for PR 6963 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/6963#issuecomment-116461218
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6963#issuecomment-116461392
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/6963#issuecomment-116461466
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/7077#issuecomment-116461351
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/7078#issuecomment-116478824
[Test build #35966 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35966/consoleFull)
for PR 7078 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7078#issuecomment-116478296
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/7078#issuecomment-116478360
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/6394#issuecomment-116484205
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/6976#issuecomment-116483736
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6394#issuecomment-116486247
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6394#issuecomment-116486215
[Test build #35970 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35970/console)
for PR 6394 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7078
---
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/6982#issuecomment-116518107
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6982#issuecomment-116518075
[Test build #35974 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35974/console)
for PR 6982 at commit
Github user tarekauel commented on the pull request:
https://github.com/apache/spark/pull/6963#issuecomment-116458925
@davies okay I changed it. Can you trigger Jenkins?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7065#issuecomment-116458114
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/7065#issuecomment-116458262
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 piaozhexiu opened a pull request:
https://github.com/apache/spark/pull/7078
[SPARK-8355] [SQL] Python DataFrameReader/Writer should mirror Scala
I compared PySpark DataFrameReader/Writer against Scala ones. `Option`
function is missing in both reader and writer, but the
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/7071#issuecomment-116499706
As you can see the captures, the time I wait until I can view the page was
not so different between before patching and after.
And as I mentioned above, I was made
GitHub user dbtsai opened a pull request:
https://github.com/apache/spark/pull/7080
[SPARK-8700][ML] Disable feature scaling in Logistic Regression
All compressed sensing applications, and some of the regression use-cases
will have better result by turning the feature scaling off.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6750#issuecomment-116876304
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/7031#issuecomment-116876711
LGTM, once you finished all the TODOs.
---
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 davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/6444#discussion_r33526720
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -303,11 +319,9 @@ private[sql] abstract class SparkStrategies
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7048#issuecomment-116879485
[Test build #36052 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36052/consoleFull)
for PR 7048 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6980
---
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 davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/6444#discussion_r33526779
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/UnsafeRowConverter.scala
---
@@ -98,6 +98,19 @@ class
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/6796#issuecomment-116879298
@rtreffer Yeah, it's intended. As explained above, this feature flag must
be set to `false` for now because the write path hasn't been refactored to
respect the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6921#issuecomment-116884712
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6921#issuecomment-116884532
[Test build #36044 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36044/console)
for PR 6921 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-116887043
OK merging into 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7031#issuecomment-116887073
[Test build #36056 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36056/consoleFull)
for PR 7031 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6557
---
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 chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/7035#discussion_r33531548
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/math.scala
---
@@ -188,6 +189,87 @@ case class Rint(child:
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/7035#discussion_r33531583
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/math.scala
---
@@ -188,6 +189,87 @@ case class Rint(child:
Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/7080#discussion_r33532097
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/classification/LogisticRegressionSuite.scala
---
@@ -208,8 +208,11 @@ class LogisticRegressionSuite
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/7036#issuecomment-116895824
Seems that the `/*` in this line starts a new comment block and fails
Jenkins:
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/6870#issuecomment-116895843
Thanks @andrewor14 and @davies , I will take a look at #3541 , from my
cursory look, I think both the target and implementation is a little different.
---
If your
Github user navis commented on the pull request:
https://github.com/apache/spark/pull/6931#issuecomment-116902528
@andrewor14 Currently, timestamp == string converts string into
timestamp, but for timestamp string, string is converted into timestamp.
And this inconsistency makes me
Github user navis closed the pull request at:
https://github.com/apache/spark/pull/6931
---
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 yanboliang commented on the pull request:
https://github.com/apache/spark/pull/6992#issuecomment-116910026
@jkbradley OK, I will do it.
---
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/7031#issuecomment-116910005
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/7031#issuecomment-116910015
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/7100#issuecomment-116910101
Thanks. I am merging it to master and branch 1.4.
---
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/7031#issuecomment-116910292
[Test build #36063 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36063/consoleFull)
for PR 7031 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6856
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/7048
---
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/7107#issuecomment-116913322
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/7077#issuecomment-116913687
Yeah, in this case it looks like a legitimate failure.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7077#issuecomment-116913517
I'm not sure if this is flaky... this particular test has failed a bunch of
times in a row for this PR, so unless we've been unusually unlucky I think that
there
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7107#issuecomment-116913302
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 jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/6894#discussion_r33535385
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/feature/DiscreteCosineTransformerSuite.scala
---
@@ -0,0 +1,88 @@
+/*
+ * Licensed to the
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/7107#issuecomment-116918029
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 this
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/6982#discussion_r33536204
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/ExtractValue.scala
---
@@ -209,4 +257,16 @@ case class GetMapValue(child:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7069#issuecomment-116924268
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/7069#issuecomment-116924326
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 andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/6743#discussion_r33536802
--- Diff: core/src/main/scala/org/apache/spark/api/r/RRDD.scala ---
@@ -390,9 +386,10 @@ private[r] object RRDD {
thread
}
-
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/6743#discussion_r33536800
--- Diff: core/src/main/scala/org/apache/spark/deploy/RRunner.scala ---
@@ -71,9 +71,10 @@ object RRunner {
val builder = new
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/7109#discussion_r33536789
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/math.scala
---
@@ -239,61 +231,13 @@ case class Bin(child: Expression)
}
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7072#issuecomment-116931991
@srowen are you strongly against this or just mildly?
---
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 a diff in the pull request:
https://github.com/apache/spark/pull/6743#discussion_r33537183
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -339,6 +340,24 @@ object SparkSubmit {
}
}
+
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6973#issuecomment-116933126
[Test build #36077 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36077/consoleFull)
for PR 6973 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7036#issuecomment-116933111
I don't think it would be super-hard to have the PR script automatically
warn us when merging a PR that has failed its most recent test run (or which
hasn't been
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7110#issuecomment-116934991
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7110#issuecomment-116935068
[Test build #36079 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36079/consoleFull)
for PR 7110 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/7049#issuecomment-116876095
Yeah, it seems this is more closely related to
https://issues.apache.org/jira/browse/SPARK-8125
/cc @liancheng
---
If your project is set up for it, you can
801 - 900 of 1332 matches
Mail list logo
