Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6880#issuecomment-113145019
[Test build #35125 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35125/consoleFull)
for PR 6880 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6262#issuecomment-113145071
[Test build #35126 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35126/consoleFull)
for PR 6262 at commit
Github user yijieshen commented on the pull request:
https://github.com/apache/spark/pull/6881#issuecomment-113145106
I prefer to keep the origin column names in the newly created struct, since
I think it's more meaningful than `col1, col2, col3`, and we could just leave
the unnamed
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6882#issuecomment-113145081
[Test build #35129 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35129/consoleFull)
for PR 6882 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6877#issuecomment-113145010
[Test build #35128 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35128/consoleFull)
for PR 6877 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6881#issuecomment-113146743
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 chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/6843#discussion_r32727925
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringOperations.scala
---
@@ -313,3 +313,131 @@ case class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6878#issuecomment-113109990
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/6878#issuecomment-113109866
[Test build #35120 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35120/console)
for PR 6878 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6875#issuecomment-113121395
Build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6881#issuecomment-113144419
[Test build #35127 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35127/consoleFull)
for PR 6881 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6262#issuecomment-113144080
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/5707#issuecomment-113149919
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/5707#issuecomment-113149945
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/6875#issuecomment-113121333
[Test build #35122 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35122/console)
for PR 6875 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5708#discussion_r32720959
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -926,7 +926,9 @@ class SparkContext(config: SparkConf) extends Logging
with
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/6881#issuecomment-113124607
@yijieshen
---
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 chenghao-intel opened a pull request:
https://github.com/apache/spark/pull/6882
[SPARK-7862] [SQL] Disable the error message redirect to stderr
This is a follow up of #6404, the ScriptTransformation prints the error msg
into stderr directly, probably be a disaster for
Github user yijieshen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6874#discussion_r32726438
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/complexTypes.scala
---
@@ -79,3 +80,44 @@ case class
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/6881#issuecomment-113150996
Ok, sound reasonable to me, closing this PR.
---
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/6843#issuecomment-113160423
[Test build #35132 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35132/consoleFull)
for PR 6843 at commit
Github user EugenCepoi commented on a diff in the pull request:
https://github.com/apache/spark/pull/5708#discussion_r32720782
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -926,7 +926,9 @@ class SparkContext(config: SparkConf) extends Logging
with
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/6874#discussion_r32724856
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/functions.scala ---
@@ -737,6 +735,21 @@ object functions {
}
/**
+ *
GitHub user chenghao-intel opened a pull request:
https://github.com/apache/spark/pull/6881
[SPARK-8283][SQL] CreateStruct should not specify the field names
`CreateStruct` = `GenericUDFStruct` which always give the default column
names for the output struct like (col1,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6882#issuecomment-113144079
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/6877#issuecomment-113144078
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/6879#issuecomment-113143934
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/6879#issuecomment-113143840
[Test build #35124 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35124/console)
for PR 6879 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6881#issuecomment-113144081
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/6880#issuecomment-113144077
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 yijieshen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6874#discussion_r32726086
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/functions.scala ---
@@ -737,6 +735,21 @@ object functions {
}
/**
+ *
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6262#issuecomment-113112104
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/6877#issuecomment-113111717
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/6877#issuecomment-113111606
[Test build #35119 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35119/console)
for PR 6877 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5707#issuecomment-113150494
[Test build #35131 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35131/consoleFull)
for PR 5707 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6843#issuecomment-113159214
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/6881#issuecomment-113125643
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/6877#issuecomment-113136109
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/6882#issuecomment-113137581
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 chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/6804#issuecomment-113149719
Probably be `Nonnull`, this will give more strict check by FindBug. It will
be great if you can run FindBug locally after the change.
---
If your project is set
Github user chenghao-intel closed the pull request at:
https://github.com/apache/spark/pull/6881
---
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
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/6874#discussion_r32724484
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/complexTypes.scala
---
@@ -79,3 +80,44 @@ case class
Github user yijieshen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6874#discussion_r32725827
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/functions.scala ---
@@ -737,6 +735,21 @@ object functions {
}
/**
+ *
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6881#issuecomment-113146910
[Test build #35130 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35130/consoleFull)
for PR 6881 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5708#discussion_r32719742
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -926,7 +926,9 @@ class SparkContext(config: SparkConf) extends Logging
with
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/6874#discussion_r32724921
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/functions.scala ---
@@ -737,6 +735,21 @@ object functions {
}
/**
+ *
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6881#issuecomment-113146720
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/6843#issuecomment-113159272
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 smola commented on a diff in the pull request:
https://github.com/apache/spark/pull/6326#discussion_r32732289
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -228,7 +228,12 @@ class SqlParser extends AbstractSparkSQLParser
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6262#issuecomment-113165776
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/4055#issuecomment-113169097
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/4055#issuecomment-113169123
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 dibbhatt commented on the pull request:
https://github.com/apache/spark/pull/6707#issuecomment-113174385
hi @tdas . Let me know if latest changes are fine
---
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/6883#issuecomment-113178842
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/6262#issuecomment-113184674
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/6262#issuecomment-113184578
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 koeninger commented on the pull request:
https://github.com/apache/spark/pull/6862#issuecomment-113184801
I'm not a python programmer, but isn't the direct translation of that
kafkaStreams = map(lambda _:KafkaUtils.createStream(...), range(0,
numStreams))
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6881#issuecomment-113169281
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 yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/6824#issuecomment-113181215
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6686#issuecomment-113189491
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/6686#issuecomment-113189528
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/6843#issuecomment-113191198
[Test build #35132 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35132/console)
for PR 6843 at commit
Github user smola commented on the pull request:
https://github.com/apache/spark/pull/6326#issuecomment-113166469
@marmbrus Done.
---
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/6881#issuecomment-113166685
[Test build #35127 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35127/console)
for PR 6881 at commit
Github user suyanNone commented on the pull request:
https://github.com/apache/spark/pull/4055#issuecomment-113166545
@andrewor14 @srowen Already refine with the comments.
---
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/4055#issuecomment-113166266
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/4055#issuecomment-113166319
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/6881#issuecomment-113166774
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/4055#issuecomment-113166827
[Test build #35133 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35133/consoleFull)
for PR 4055 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4055#issuecomment-113169866
[Test build #35134 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35134/consoleFull)
for PR 4055 at commit
Github user hntd187 commented on the pull request:
https://github.com/apache/spark/pull/1290#issuecomment-11317
@avulanov Also, we're going to have to add a dependency with this with the
HDF5 library, I think this should be handled the way the netlib is handled with
the user
Github user EugenCepoi commented on a diff in the pull request:
https://github.com/apache/spark/pull/5708#discussion_r32741755
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -926,7 +926,9 @@ class SparkContext(config: SparkConf) extends Logging
with
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6647#issuecomment-113190638
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/4055#issuecomment-113167204
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/4055#issuecomment-113167200
[Test build #35133 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35133/console)
for PR 4055 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6882#issuecomment-113177974
[Test build #35129 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35129/console)
for PR 6882 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6882#issuecomment-113178136
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/6824#issuecomment-113182938
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/6824#issuecomment-113182987
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/6824#issuecomment-113183907
[Test build #35135 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35135/consoleFull)
for PR 6824 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6877#issuecomment-113188524
[Test build #35128 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35128/console)
for PR 6877 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6647#issuecomment-113190675
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/6647#issuecomment-113196994
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/6647#issuecomment-113196957
[Test build #35138 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35138/console)
for PR 6647 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6262#issuecomment-113165679
[Test build #35126 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35126/console)
for PR 6262 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5707#issuecomment-113169048
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 koertkuipers opened a pull request:
https://github.com/apache/spark/pull/6883
SPARK-4644 blockjoin
Although the discussion (and design doc) under SPARK-4644 seem focussed on
other aspects of skew (OOM mostly) than this pullreq (which focusses on
avoiding a single
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6262#issuecomment-113184900
[Test build #35136 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35136/consoleFull)
for PR 6262 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6877#issuecomment-113188582
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/6686#issuecomment-113190209
[Test build #35137 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35137/consoleFull)
for PR 6686 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6647#issuecomment-113191390
[Test build #35138 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35138/consoleFull)
for PR 6647 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4055#issuecomment-113191005
[Test build #35134 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35134/console)
for PR 4055 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4055#issuecomment-113191053
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/6843#issuecomment-113191227
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/5707#issuecomment-113169006
[Test build #35131 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35131/console)
for PR 5707 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6881#issuecomment-113169252
[Test build #35130 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35130/console)
for PR 6881 at commit
Github user smola commented on the pull request:
https://github.com/apache/spark/pull/6853#issuecomment-113169112
@marmbrus Yes, this patch is meant just to delay the check until check
analysis. The reason is that just because ResolveReferences rule cannot resolve
the plan, that does
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6880#issuecomment-113197110
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 a diff in the pull request:
https://github.com/apache/spark/pull/6862#discussion_r32744362
--- Diff: docs/streaming-programming-guide.md ---
@@ -1937,6 +1937,16 @@ JavaPairDStreamString, String unifiedStream =
streamingContext.union(kafkaStre
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6880#issuecomment-113197083
**[Test build #35125 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35125/console)**
for PR 6880 at commit
1 - 100 of 1300 matches
Mail list logo
