GitHub user pavel-sakun opened a pull request:
https://github.com/apache/spark/pull/5202
SPARK-6549 - Spark console logger logs to stderr by default
Changed default log4j configuration to log into stdout by default
You can merge this pull request into a Git repository by running:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5203#issuecomment-86408710
Test FAILed.
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/5198#issuecomment-86411873
@DoingDone9 Would you mind to add your name to JIRA and GitHub, so that we
can include your name in the credit list of the next release? Also, please add
your name in
Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/5116#issuecomment-86416624
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
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/5204#issuecomment-86417578
ok, I have closed 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 your project does not have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5204#issuecomment-86437440
[Test build #29221 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29221/consoleFull)
for PR 5204 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5205#issuecomment-86445215
[Test build #29220 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29220/consoleFull)
for PR 5205 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5205#issuecomment-86445228
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/5203
[SPARK-6550][SQL] Add PreAnalyzer to keep logical plan consistent across
DataFrame
## Problems
In some cases, the expressions in a logical plan will be modified to new
ones during
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5203#issuecomment-86408687
[Test build #29219 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29219/consoleFull)
for PR 5203 at commit
Github user witgo closed the pull request at:
https://github.com/apache/spark/pull/5204
---
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/5206#issuecomment-86420171
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/5207#issuecomment-86429498
[Test build #29223 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29223/consoleFull)
for PR 5207 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5178#issuecomment-86430853
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/5178#issuecomment-86430835
**[Test build #29217 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29217/consoleFull)**
for PR 5178 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5202#issuecomment-86403254
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 DoingDone9 commented on the pull request:
https://github.com/apache/spark/pull/5198#issuecomment-86416015
ok i will change @liancheng
---
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 witgo opened a pull request:
https://github.com/apache/spark/pull/5204
[Hot Fix][SQL] a compilation error in InsertIntoHiveTableSuite.scala
cc @marmbrus
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark
Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/5202#issuecomment-86416244
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user zzcclp commented on the pull request:
https://github.com/apache/spark/pull/5204#issuecomment-86416823
@witgo , This [PR](https://github.com/apache/spark/pull/5198) has resolved
the problem.
---
If your project is set up for it, you can reply to this email and have your
GitHub user WangTaoTheTonic opened a pull request:
https://github.com/apache/spark/pull/5205
[SPARK-6552][Deploy][Doc]expose start-slave.sh to user and update outdated
doc
https://issues.apache.org/jira/browse/SPARK-6552
/cc @srowen
You can merge this pull request into a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5204#issuecomment-86437830
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/5201#issuecomment-86409494
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/5201#issuecomment-86409461
[Test build #29216 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29216/consoleFull)
for PR 5201 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5116#issuecomment-86417226
[Test build #29222 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29222/consoleFull)
for PR 5116 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5204#issuecomment-86417237
[Test build #29221 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29221/consoleFull)
for PR 5204 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5178#issuecomment-86433963
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
GitHub user adrian-wang opened a pull request:
https://github.com/apache/spark/pull/5208
[SPARK-2213] [SQL] sort merge join for spark sql
Thanks for the initial work from @Ishiihara in #3173
You can merge this pull request into a Git repository by running:
$ git pull
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5203#issuecomment-86404039
[Test build #29219 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29219/consoleFull)
for PR 5203 at commit
Github user chidouhu commented on a diff in the pull request:
https://github.com/apache/spark/pull/5197#discussion_r27196269
--- Diff:
core/src/main/scala/org/apache/spark/network/BlockTransferService.scala ---
@@ -83,7 +83,12 @@ abstract class BlockTransferService extends
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/5198#issuecomment-86415027
Merged into master, 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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/5198
---
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 commented on the pull request:
https://github.com/apache/spark/pull/5203#issuecomment-86417077
The test failure is caused by another commit and just fixed in #5198.
Please test it again.
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5205#issuecomment-86417149
[Test build #29220 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29220/consoleFull)
for PR 5205 at commit
GitHub user ksonj opened a pull request:
https://github.com/apache/spark/pull/5206
[SPARK-6553] [pyspark] Support functools.partial as UDF
Use `f.__repr__()` instead of `f.__name__` when instantiating
`UserDefinedFunction`s, so `functools.partial`s may be used.
You can merge this
GitHub user hhbyyh opened a pull request:
https://github.com/apache/spark/pull/5207
[MLlib]remove unused import
minor thing. Let me know if jira is required.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hhbyyh/spark
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5178#issuecomment-86433945
**[Test build #29218 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29218/consoleFull)**
for PR 5178 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5208#issuecomment-86433992
[Test build #29224 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29224/consoleFull)
for PR 5208 at commit
Github user saucam commented on the pull request:
https://github.com/apache/spark/pull/5141#issuecomment-86443584
hi @liancheng , thanks for reviewing.
One small query on a separate note,
currently in the implementation of mergeMetastoreParquetSchema, I see that
for
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5208#issuecomment-86443175
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/5208#issuecomment-86443152
[Test build #29224 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29224/consoleFull)
for PR 5208 at commit
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/5191#issuecomment-86448122
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/5191#issuecomment-86449172
Thanks, merged to master and 1.3.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/5191
---
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/5116#issuecomment-86456656
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/5207#issuecomment-86460036
[Test build #29223 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29223/consoleFull)
for PR 5207 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5207#issuecomment-86460091
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/5209
[SPARK-6556][Core] Fix wrong parsing logic of executorTimeoutMs and
checkTimeoutIntervalMs in HeartbeatReceiver
The current reading logic of `executorTimeoutMs` is:
```Scala
private val
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5205#discussion_r27206723
--- Diff: sbin/start-slave.sh ---
@@ -17,8 +17,14 @@
# limitations under the License.
#
-# Usage: start-slave.sh worker# master-spark-URL
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5209#discussion_r27206977
--- Diff: core/src/main/scala/org/apache/spark/HeartbeatReceiver.scala ---
@@ -49,12 +49,13 @@ private[spark] class HeartbeatReceiver(sc:
SparkContext,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5116#issuecomment-86456646
**[Test build #29222 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29222/consoleFull)**
for PR 5116 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5193#issuecomment-86459524
We should probably sync this to the underlying Hadoop version. However I
know this already doesn't match it and I suspect that bumping a maintenance
release won't hurt.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5181#issuecomment-86479192
[Test build #29225 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29225/consoleFull)
for PR 5181 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5202#issuecomment-86482979
No, I'm pretty certain this is on purpose. This change makes log output mix
with program output. You can override it in your own logging config if you
like.
---
If
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5205#discussion_r27206724
--- Diff: docs/spark-standalone.md ---
@@ -24,7 +24,7 @@ the master's web UI, which is
[http://localhost:8080](http://localhost:8080) by
Similarly,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5209#issuecomment-86484779
[Test build #29226 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29226/consoleFull)
for PR 5209 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5207#issuecomment-86452943
@hhbyyh this kind of thing is too insignificant to bother with, as it still
consumes nontrivial time to review and merge.
---
If your project is set up for it, you can
Github user yishenggudou commented on the pull request:
https://github.com/apache/spark/pull/5206#issuecomment-86463666
~_~
---
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 WangTaoTheTonic commented on a diff in the pull request:
https://github.com/apache/spark/pull/5205#discussion_r27211048
--- Diff: docs/spark-standalone.md ---
@@ -24,7 +24,7 @@ the master's web UI, which is
[http://localhost:8080](http://localhost:8080) by
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5205#issuecomment-86511598
[Test build #29230 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29230/consoleFull)
for PR 5205 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5148#issuecomment-86511648
[Test build #29231 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29231/consoleFull)
for PR 5148 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5209#issuecomment-86512683
[Test build #29226 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29226/consoleFull)
for PR 5209 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5209#issuecomment-86512694
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/5207
---
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5074#discussion_r27212304
--- Diff: docs/programming-guide.md ---
@@ -1086,6 +1086,66 @@ for details.
/tr
/table
+### Shuffle operations
+
+Certain
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5209#issuecomment-86490567
[Test build #29227 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29227/consoleFull)
for PR 5209 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4869#issuecomment-86498365
Build and test fixes warm my heart. Excellent!
---
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 liancheng opened a pull request:
https://github.com/apache/spark/pull/5210
[SPARK-6554] [SQL] Don't push down predicates which reference partition
column(s)
There are two cases for the new Parquet data source:
1. Partition columns exist in the Parquet data
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5148#issuecomment-86503902
@FRosner this path is tested by the existing unit tests, but I'll add
another test per my last comment, and some comments here.
---
If your project is set up for it, you
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/5141#issuecomment-86507585
@marmbrus @saucam Confirmed that 1.2 actually works in this case. So this
is a regression. Merging to master and 1.3. Thanks for working on this and the
comments!
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/5209#discussion_r27208000
--- Diff: core/src/main/scala/org/apache/spark/HeartbeatReceiver.scala ---
@@ -49,12 +49,13 @@ private[spark] class HeartbeatReceiver(sc:
SparkContext,
Github user pavel-sakun commented on the pull request:
https://github.com/apache/spark/pull/5202#issuecomment-86491813
Isn't it why loggers/levels/categories and all that stuff exist? Stderr as
it's name implies should be used for error messages. In case of submitting job
to yarn
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5202#issuecomment-86495944
`stderr` is just a name; I read it as a side-channel for output that is
different from program output. It can be for error messages, but is not
inherently only for error
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/5136
---
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 FRosner commented on a diff in the pull request:
https://github.com/apache/spark/pull/5148#discussion_r27209470
--- Diff: core/src/main/scala/org/apache/spark/rdd/DoubleRDDFunctions.scala
---
@@ -191,25 +191,22 @@ class DoubleRDDFunctions(self: RDD[Double]) extends
Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/5116#issuecomment-86503946
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
Github user FRosner commented on the pull request:
https://github.com/apache/spark/pull/5148#issuecomment-86504324
Thanks. Unit tests and scala doc help to document the interface /
parameters and expected behaviour of a function so I like them a lot :smile:
---
If your project is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5116#issuecomment-86504656
[Test build #29229 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29229/consoleFull)
for PR 5116 at commit
Github user WangTaoTheTonic commented on a diff in the pull request:
https://github.com/apache/spark/pull/5205#discussion_r27210539
--- Diff: sbin/start-slave.sh ---
@@ -17,8 +17,14 @@
# limitations under the License.
#
-# Usage: start-slave.sh worker#
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5199#discussion_r27209161
--- Diff:
core/src/main/scala/org/apache/spark/util/collection/CompactBuffer.scala ---
@@ -152,6 +152,20 @@ private[spark] class CompactBuffer[T: ClassTag]
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5210#issuecomment-86501156
[Test build #29228 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29228/consoleFull)
for PR 5210 at commit
Github user lianhuiwang commented on the pull request:
https://github.com/apache/spark/pull/5209#issuecomment-86504920
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5181#issuecomment-86508308
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/5181#issuecomment-86508281
[Test build #29225 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29225/consoleFull)
for PR 5181 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/5141
---
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/5212#issuecomment-86789308
[Test build #29271 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29271/consoleFull)
for PR 5212 at commit
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/5205#issuecomment-86790610
I just thought that this create the chance to make the variables in
spark-env.sh to be inconsistent with what are actually in usethough it
might be just a minor
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/5218#issuecomment-86807495
LGTM pending 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 your project does not have this
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/5009#issuecomment-86809275
Final stretch! I just need to update the docs now.
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/5219#issuecomment-86812865
Jenkins, 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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5094#issuecomment-86819348
[Test build #29275 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29275/consoleFull)
for PR 5094 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5094#issuecomment-86819376
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/5218#issuecomment-86823849
[Test build #29277 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29277/consoleFull)
for PR 5218 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5218#issuecomment-86823880
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/3247#issuecomment-86826822
[Test build #29286 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29286/consoleFull)
for PR 3247 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3247#issuecomment-86826897
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/5223#issuecomment-86834742
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/5223#issuecomment-86834738
[Test build #29280 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29280/consoleFull)
for PR 5223 at commit
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/5084#issuecomment-86835246
Yeah I agree with Sean and what pretty much everyone else said.
My feeling is that we don't want typical spark users to be relying on
unstable API's, else it
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/5175#issuecomment-86789060
Thanks! Merged 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
1 - 100 of 483 matches
Mail list logo
