Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3381#issuecomment-64322393
[Test build #23827 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23827/consoleFull)
for PR 3381 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3429#issuecomment-64322381
[Test build #23826 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23826/consoleFull)
for PR 3429 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3435#issuecomment-64322398
[Test build #23825 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23825/consoleFull)
for PR 3435 at commit
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/3447
[SPARK-4592] Avoid duplicate worker registrations in standalone mode
**Symptom.** On failover, the Master may receive duplicate registrations
from the same worker, causing the worker to exit.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3443#issuecomment-64323518
[Test build #23821 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23821/consoleFull)
for PR 3443 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3443#issuecomment-64323521
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3429#issuecomment-64323707
[Test build #23829 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23829/consoleFull)
for PR 3429 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3447#issuecomment-64323736
[Test build #23828 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23828/consoleFull)
for PR 3447 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2828#issuecomment-64323860
Andrew's got a patch for this: #3447
---
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 Leolh opened a pull request:
https://github.com/apache/spark/pull/3448
[SPARK-4594][SQL] Improvement the broadcast for HiveConf
https://issues.apache.org/jira/browse/SPARK-4594
Every time we need to get a table from hive , HadoopTableReader will
broadcast HiveConf
Github user Leolh closed the pull request at:
https://github.com/apache/spark/pull/3448
---
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 viirya opened a pull request:
https://github.com/apache/spark/pull/3449
[SPARK-4597] Use proper exception and reset variable
`File.exists()` and `File.mkdirs()` only throw `SecurityException` instead
of `IOException`. Then, when an exception is thrown, `dir` should be
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3399#issuecomment-64324351
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3399#issuecomment-64324344
[Test build #23820 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23820/consoleFull)
for PR 3399 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3449#issuecomment-64324372
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3449#issuecomment-64324781
Jenkins, this is 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3447#issuecomment-64324812
[Test build #23830 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23830/consoleFull)
for PR 3447 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3449#issuecomment-64325487
[Test build #23831 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23831/consoleFull)
for PR 3449 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3429#issuecomment-64325735
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/3429#issuecomment-64325733
[Test build #23826 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23826/consoleFull)
for PR 3429 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3386#issuecomment-64325757
[Test build #23832 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23832/consoleFull)
for PR 3386 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3247#issuecomment-64325755
[Test build #23833 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23833/consoleFull)
for PR 3247 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3247#issuecomment-64325852
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/3247#issuecomment-64325848
[Test build #23833 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23833/consoleFull)
for PR 3247 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/3449#discussion_r20849000
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -262,7 +262,7 @@ private[spark] object Utils extends Logging {
if
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/3449#discussion_r20849117
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -262,7 +262,7 @@ private[spark] object Utils extends Logging {
if
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3445#issuecomment-64326886
[Test build #23823 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23823/consoleFull)
for PR 3445 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3445#issuecomment-64326891
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/3429#issuecomment-64327084
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/3429#issuecomment-64327080
[Test build #23829 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23829/consoleFull)
for PR 3429 at commit
GitHub user adrian-wang opened a pull request:
https://github.com/apache/spark/pull/3450
[SPARK-4599] [Build] [SQL] add hive profile in root pom
This is what it was after #2685 , but seems reset by #3159
You can merge this pull request into a Git repository by running:
$ git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3450#issuecomment-64327986
[Test build #23834 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23834/consoleFull)
for PR 3450 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3444#issuecomment-64328090
[Test build #23822 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23822/consoleFull)
for PR 3444 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/3450#discussion_r20849854
--- Diff: pom.xml ---
@@ -1394,7 +1394,7 @@
/dependencies
/profile
profile
- idhive-thriftserver/id
+ idhive/id
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3444#issuecomment-64328095
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user adrian-wang commented on a diff in the pull request:
https://github.com/apache/spark/pull/3450#discussion_r20850064
--- Diff: pom.xml ---
@@ -1394,7 +1394,7 @@
/dependencies
/profile
profile
- idhive-thriftserver/id
+
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3381#issuecomment-64328732
[Test build #23827 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23827/consoleFull)
for PR 3381 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3381#issuecomment-64328742
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/3386#issuecomment-64329427
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/3386#issuecomment-64329419
[Test build #23832 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23832/consoleFull)
for PR 3386 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3447#issuecomment-64330152
[Test build #23835 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23835/consoleFull)
for PR 3447 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3446#issuecomment-64330374
[Test build #23824 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23824/consoleFull)
for PR 3446 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3446#issuecomment-64330381
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3435#issuecomment-64331011
[Test build #23825 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23825/consoleFull)
for PR 3435 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3435#issuecomment-64331017
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user lowryact opened a pull request:
https://github.com/apache/spark/pull/3451
Branch 1.0
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/spark branch-1.0
Alternatively you can review and apply these changes as
GitHub user Leolh opened a pull request:
https://github.com/apache/spark/pull/3452
[SPARK-4594][SQL] Improvement the broadcast for HiveConf
Every time we need to get a table from hive , HadoopTableReader will
broadcast HiveConf to clustor . Acturally In one application the hiveconf
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3452#issuecomment-64331829
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3451#issuecomment-64331834
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/3447#issuecomment-64332172
[Test build #23828 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23828/consoleFull)
for PR 3447 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/3451#issuecomment-64332167
This PR looks messed up or opened in error, can it be closed?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3447#issuecomment-64332179
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/3381#issuecomment-64332371
@adrian-wang Yea, Jenkins compiles Spark SQL with both Hive 0.12.0 and
0.13.1, and then runs SQL tests against 0.13.1.
---
If your project is set up for it, you can
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3447#issuecomment-64336089
[Test build #23830 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23830/consoleFull)
for PR 3447 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3447#issuecomment-64336176
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user mengxr opened a pull request:
https://github.com/apache/spark/pull/3453
[Spark-4509] Revert EC2 tag-based cluster membership patch
This PR reverts changes related to tag-based cluster membership. As
discussed in SPARK-3332, we didn't figure out a safe strategy to use
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/3435#discussion_r20852499
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/feature/StandardScaler.scala ---
@@ -97,30 +97,57 @@ class StandardScalerModel private[mllib] (
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3449#issuecomment-64344035
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3449#issuecomment-64344002
[Test build #23831 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23831/consoleFull)
for PR 3449 at commit
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/3446#issuecomment-64345544
LGTM. Merged into master and branch-1.2. 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3453#issuecomment-64347503
[Test build #23836 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23836/consoleFull)
for PR 3453 at commit
Github user ueshin commented on the pull request:
https://github.com/apache/spark/pull/3405#issuecomment-64351835
Hi, is this related to #3058?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/3399#issuecomment-64354201
LGTM. Merged into master and branch-1.2. The JIRA number should be
SPARK-4530 instead of SPARK-4526. Could you update the title and then close
this PR? Thanks!
---
If
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/3439#discussion_r20853259
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/tree/loss/SquaredError.scala ---
@@ -49,18 +48,17 @@ object SquaredError extends Loss {
}
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3450#issuecomment-64376530
[Test build #23834 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23834/consoleFull)
for PR 3450 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3450#issuecomment-64376615
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3447#issuecomment-64381651
[Test build #23835 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23835/consoleFull)
for PR 3447 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3447#issuecomment-64381659
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/3399#issuecomment-64381732
@mengxr The title has been updated.
---
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 srowen opened a pull request:
https://github.com/apache/spark/pull/3454
SPARK-1450 [EC2] Specify the default zone in the EC2 script help
This looks like a one-liner, so I took a shot at it. There can be no fixed
default availability zone since the names are different
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3454#issuecomment-64382910
[Test build #23837 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23837/consoleFull)
for PR 3454 at commit
GitHub user KaiXinXiaoLei reopened a pull request:
https://github.com/apache/spark/pull/3224
Delete unnecessary function
when building spark by sbt, the function ârunAlternateBoot in
sbt/sbt-launch-lib.bash is not used. And this function is not used by spark
code. So I think
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3224#issuecomment-64384870
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 KaiXinXiaoLei commented on the pull request:
https://github.com/apache/spark/pull/3224#issuecomment-64385026
The file from https://github.com/sbt/sbt-launcher-package is changed. And
the function ârunAlternateBoot is deleted in upstream project. I think
spark project
Github user KaiXinXiaoLei commented on the pull request:
https://github.com/apache/spark/pull/3224#issuecomment-64385336
The file from https://github.com/sbt/sbt-launcher-package is changed. And
the function ârunAlternateBoot is deleted in upstream project. I think spark
project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3453#issuecomment-64386611
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3453#issuecomment-64386599
[Test build #23836 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23836/consoleFull)
for PR 3453 at commit
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/3400#issuecomment-64389631
@watermen Thanks these are great fixes.
---
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 tdas commented on the pull request:
https://github.com/apache/spark/pull/3400#issuecomment-64389589
Jenkins, this is 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3400#issuecomment-64390206
[Test build #23838 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23838/consoleFull)
for PR 3400 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3454#issuecomment-64391330
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3454#issuecomment-64391321
[Test build #23837 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23837/consoleFull)
for PR 3454 at commit
GitHub user tdas opened a pull request:
https://github.com/apache/spark/pull/3455
[SPARK-4601][Streaming] Set correct call site for streaming jobs so that it
is displayed correctly on the Spark UI
When running the NetworkWordCount, the description of the word count jobs
are set as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3455#issuecomment-64398664
[Test build #23839 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23839/consoleFull)
for PR 3455 at commit
GitHub user XuTingjun opened a pull request:
https://github.com/apache/spark/pull/3456
[SPARK-4598] use pagination to show tasktable
When the application has too many tasks, tasktable with all tasks costs a
lot of memory. If using pagination, every time tasktable shows some tasks.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3456#issuecomment-64398877
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/3400#issuecomment-64398984
[Test build #23838 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23838/consoleFull)
for PR 3400 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3400#issuecomment-64398987
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/3244#issuecomment-64399467
Since no unit tests cover this change, I tested it manually. It works as
expected merging this.
---
If your project is set up for it, you can reply to this email and have
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/3409#discussion_r20864416
--- Diff: conf/spark-defaults.conf.template ---
@@ -8,3 +8,4 @@
# spark.serializer
org.apache.spark.serializer.KryoSerializer
#
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/3403#issuecomment-64405670
I agree with Sandy on this, can you close this until we get SPARK-2089
working and then we can make sure it works with Java api also.
---
If your project is set up
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/3209#issuecomment-64405811
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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/3209#issuecomment-64405912
@vanzin I think I'll pull this in and you will have to remove it again in
https://github.com/apache/spark/pull/3233
---
If your project is set up for it, you can
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/3209#issuecomment-64406285
I pulled this into both master and branch-1.2
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3316#issuecomment-64406710
[Test build #23840 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23840/consoleFull)
for PR 3316 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3386#issuecomment-64407794
[Test build #23841 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23841/consoleFull)
for PR 3386 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3455#issuecomment-64409916
[Test build #23839 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23839/consoleFull)
for PR 3455 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3455#issuecomment-64409929
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user tdas opened a pull request:
https://github.com/apache/spark/pull/3457
[SPARK-4196][SPARK-4602] Fix serialization issue in
PairDStreamFunctions.saveAsNewAPIHadoopFiles
Solves two JIRAs in one shot
- Makes the ForechDStream created by saveAsNewAPIHadoopFiles
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/3457#discussion_r20868146
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/PairDStreamFunctions.scala
---
@@ -702,11 +699,14 @@ class PairDStreamFunctions[K,
1 - 100 of 336 matches
Mail list logo
