Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168339017
**[Test build #2289 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2289/consoleFull)**
for PR 10525 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10548#issuecomment-168345746
**[Test build #48572 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48572/consoleFull)**
for PR 10548 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10549#issuecomment-168361621
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 HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/8743#issuecomment-168367522
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10551#issuecomment-168368188
**[Test build #48577 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48577/consoleFull)**
for PR 10551 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10550#issuecomment-168368843
Test FAILed.
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/10550#issuecomment-168368840
**[Test build #48579 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48579/consoleFull)**
for PR 10550 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10550#issuecomment-168368842
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/8743#issuecomment-168367565
**[Test build #2295 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2295/consoleFull)**
for PR 8743 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10550#issuecomment-168368807
**[Test build #48579 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48579/consoleFull)**
for PR 10550 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10551#issuecomment-168368468
**[Test build #48578 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48578/consoleFull)**
for PR 10551 at commit
Github user jegonzal commented on the pull request:
https://github.com/apache/spark/pull/10550#issuecomment-168368506
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168368976
OK merging again.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10551#issuecomment-168367746
Test FAILed.
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/10551#issuecomment-168367738
**[Test build #48576 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48576/consoleFull)**
for PR 10551 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10551#issuecomment-168367745
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/10525
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8743#issuecomment-168371292
**[Test build #2295 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2295/consoleFull)**
for PR 8743 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/10542#discussion_r48680023
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -769,6 +770,63 @@ object ReorderJoin extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10548#issuecomment-168346201
**[Test build #48572 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48572/consoleFull)**
for PR 10548 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10551#issuecomment-168363206
**[Test build #48575 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48575/consoleFull)**
for PR 10551 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8743#issuecomment-168364467
**[Test build #2294 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2294/consoleFull)**
for PR 8743 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/10551#issuecomment-168365001
Failed cases are not related to the code changes.
retest this please
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10548#issuecomment-168345726
Test FAILed.
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/10548#issuecomment-168345725
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/10548#issuecomment-168346207
Test FAILed.
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/10548#issuecomment-168346206
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/10547#issuecomment-168357144
**[Test build #2292 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2292/consoleFull)**
for PR 10547 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10551#issuecomment-168367011
**[Test build #48576 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48576/consoleFull)**
for PR 10551 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168338807
**[Test build #2289 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2289/consoleFull)**
for PR 10525 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10541#issuecomment-168338815
The jira ticket is linked incorrectly I think.
---
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/8743#issuecomment-168338761
**[Test build #2287 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2287/consoleFull)**
for PR 8743 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10540
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/10511#issuecomment-168339460
I took a quick look and I'm going to merge this because I'm working on
something that conflicts with it. It would be great if @nongli or @JoshRosen
can review this more
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10544#issuecomment-168361036
This works too. I have a separate pull request that adds a new API for
this: https://github.com/apache/spark/pull/10547
---
If your project is set up for it, you can
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10511
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9608#issuecomment-168351836
**[Test build #48573 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48573/consoleFull)**
for PR 9608 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9608#issuecomment-168351853
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/9608#issuecomment-168351854
Test FAILed.
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/8743#issuecomment-168361139
**[Test build #2294 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2294/consoleFull)**
for PR 8743 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10551#issuecomment-168364748
**[Test build #48575 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48575/consoleFull)**
for PR 10551 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10551#issuecomment-168364754
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user datafarmer commented on the pull request:
https://github.com/apache/spark/pull/10546#issuecomment-168333823
@srowen I guess that I should have created a JIRA ticket first. I just
created one: SPARK-12598
---
If your project is set up for it, you can reply to this email
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168339224
@JoshRosen I pushed a commit directly to disable test-dependencies.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user rxin closed the pull request at:
https://github.com/apache/spark/pull/10548
---
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/10550#issuecomment-168362804
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/10550#issuecomment-168362805
Test FAILed.
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/10550#issuecomment-168362743
**[Test build #48574 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48574/consoleFull)**
for PR 10550 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10550#issuecomment-168362802
**[Test build #48574 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48574/consoleFull)**
for PR 10550 at commit
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/10547
[SPARK-12599][MLlib][SQL] Remove the use of callUDF in MLlib
callUDF has been deprecated. However, we do not have an alternative for
users to specify the output data type without type tags. This pull
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9608#issuecomment-168345176
**[Test build #48573 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48573/consoleFull)**
for PR 9608 at commit
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/8743#issuecomment-168346039
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8743#issuecomment-168356745
**[Test build #2291 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2291/consoleFull)**
for PR 8743 at commit
Github user jegonzal commented on the pull request:
https://github.com/apache/spark/pull/10550#issuecomment-168362426
@davies and @JoshRosen let me know what you think of this design.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
GitHub user jegonzal opened a pull request:
https://github.com/apache/spark/pull/10550
Adding zipPartitions to PySpark
The following working WIP adds support for `zipPartitions` to PySpark.
This is accomplished by modifying the PySpark `worker` (in both daemon and
non-deamon
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10542#issuecomment-168336750
**[Test build #48569 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48569/consoleFull)**
for PR 10542 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168339295
**[Test build #2290 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2290/consoleFull)**
for PR 10525 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8743#issuecomment-168339975
**[Test build #2287 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2287/consoleFull)**
for PR 8743 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10529#issuecomment-168340743
**[Test build #2288 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2288/consoleFull)**
for PR 10529 at commit
Github user radekg commented on the pull request:
https://github.com/apache/spark/pull/9608#issuecomment-168344020
I will need to verify this patch with torrent broadcast.
---
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/10547#issuecomment-168351377
Test FAILed.
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/10547#issuecomment-168351376
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 ouyangshourui opened a pull request:
https://github.com/apache/spark/pull/10549
size RollingPolicy shouldRollover loginfo should change to logDebug
https://issues.apache.org/jira/browse/SPARK-12601
when using size RollingPolicythis code cause worker output a large of
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10551#issuecomment-168364752
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/10544#issuecomment-168364756
BTW is transformFunc a public API that custom transformers are supposed to
implement? If it is, this is technically an API breaking change you are making.
---
If your
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/10551#issuecomment-168366180
retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10540#issuecomment-168338785
I've merged this.
Thanks.
---
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/10529#issuecomment-168338746
**[Test build #2288 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2288/consoleFull)**
for PR 10529 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10542#issuecomment-168341219
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/10542#issuecomment-168341218
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/10542#issuecomment-168341197
**[Test build #48569 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48569/consoleFull)**
for PR 10542 at commit
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/10548
[SPARK-12600][SQL] Remove deprecated methods in Spark SQL
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rxin/spark SPARK-12600
Alternatively
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10547#issuecomment-168343118
**[Test build #48570 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48570/consoleFull)**
for PR 10547 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10547#issuecomment-168351345
**[Test build #48570 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48570/consoleFull)**
for PR 10547 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168351298
**[Test build #2290 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2290/consoleFull)**
for PR 10525 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8743#issuecomment-168353114
**[Test build #2291 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2291/consoleFull)**
for PR 8743 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10547#issuecomment-168353154
**[Test build #2292 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2292/consoleFull)**
for PR 10547 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10547#issuecomment-168361123
**[Test build #2293 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2293/consoleFull)**
for PR 10547 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10511#issuecomment-168361081
Actually I'm going to revert this for now. I've seen two separate pull
requests that failed python tests.
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/10551
[SPARK-12602] [SQL] Join Reordering: Pushing Inner Join Through Left/Right
Outer Join
This PR is to push `Inner Join` through `Left/Right Outer Join`. This can
reduce the number of processed
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10547#issuecomment-168364250
**[Test build #2293 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2293/consoleFull)**
for PR 10547 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8743#issuecomment-168294581
Sorry I kept merging pull requests that made your life harder. Can you
bring it up to date again? I promise this is the last one.
---
If your project is set up for it,
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10534#issuecomment-168294573
LGTM. We should let @tdas take a look at this though.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168302341
**[Test build #2286 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2286/consoleFull)**
for PR 10525 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168294441
I triggered 3 more runs.
---
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/10525#issuecomment-168294453
**[Test build #2284 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2284/consoleFull)**
for PR 10525 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168294469
**[Test build #2286 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2286/consoleFull)**
for PR 10525 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168294465
**[Test build #2285 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2285/consoleFull)**
for PR 10525 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10470#issuecomment-168294357
Thanks - I've merged this.
---
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/10470
---
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/10542#discussion_r48676822
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -769,6 +770,63 @@ object ReorderJoin extends
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/10435#discussion_r48676826
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/FunctionRegistry.scala
---
@@ -278,6 +278,7 @@ object FunctionRegistry {
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168294519
cc @JoshRosen dependency failed again
---
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/10525#issuecomment-168294492
**[Test build #2285 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2285/consoleFull)**
for PR 10525 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10525#issuecomment-168301945
**[Test build #2284 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2284/consoleFull)**
for PR 10525 at commit
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/8743#issuecomment-168306690
Could anybody please type "test this please" for this PR? I can't trigger a
test for this PR.
---
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/10544#issuecomment-168312778
**[Test build #48565 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48565/consoleFull)**
for PR 10544 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10464#discussion_r48678510
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/SocketInputDStream.scala
---
@@ -51,29 +51,44 @@ class SocketReceiver[T: ClassTag](
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10464#discussion_r48678511
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/SocketInputDStream.scala
---
@@ -51,29 +51,44 @@ class SocketReceiver[T: ClassTag](
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8785#issuecomment-168313849
Weird, OK. This 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
1 - 100 of 133 matches
Mail list logo
