Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1325#issuecomment-48276050
LGTM, +1
---
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/1282#issuecomment-48276380
Merged build finished. All automated tests passed.
---
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1325#discussion_r14639677
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -112,6 +113,26 @@ object ColumnPruning extends
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1325#discussion_r14639691
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -112,6 +113,26 @@ object ColumnPruning extends
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1325#discussion_r14639717
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -112,6 +113,26 @@ object ColumnPruning extends
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1324#issuecomment-48280471
Thanks. Merging this in 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1324
---
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/1241#issuecomment-48280584
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1153#issuecomment-48280658
Thanks. Merging this in master and branch-1.0.
---
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/1241#issuecomment-48280591
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/1153
---
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/1069#issuecomment-48280716
Can one of you give me a tl;dr on the verdict about this one? :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1325#discussion_r14639873
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -112,6 +113,26 @@ object ColumnPruning extends
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1323#issuecomment-48280759
I just merged #1153 and unfortunately this one is no longer mergeable. Will
- mind updating it?
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-48280910
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/1112#issuecomment-48280916
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1321#issuecomment-48280965
Maybe we should also solve the problem that local execution should not
transfer the whole in-memory block (as a matter of fact, perhaps local
execution should just bypass
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1325#discussion_r14640036
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -112,6 +113,26 @@ object ColumnPruning extends
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-48281236
Sorry will take a look tomorrow!
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1318#issuecomment-48281300
LGTM. Merging in master branch-1.0.
---
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/1318
---
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 the pull request:
https://github.com/apache/spark/pull/1069#issuecomment-48281479
@rxin It looks like Scala is requiring developers to be more explicit about
intention to use these features; these warnings become errors in Scala 2.11
actually. So my
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1314#issuecomment-48281532
You can exclude the licensing check by editing .rat-excludes file.
One thing I'm not sure about is whether it is worth it to introduce jquery
and other library just
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1325#discussion_r14640188
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -112,6 +113,26 @@ object ColumnPruning extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1325#issuecomment-48281644
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/1325#issuecomment-48281631
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1325#issuecomment-48281746
LGTM. Let's merge once Jenkins comes back happy.
---
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/1069#issuecomment-48281718
Thanks for summarizing that. I agree that we should not have a global flag
that just disables certain warnings, since that could hide potential problems
in the future.
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1314#issuecomment-48281747
@rxin what if we merged this as-is and then we create a starter jira to
write a small library for doing tooltips and remove jquery? I think
@kayousterhout probably
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1284#issuecomment-48281934
@XuTingjun Do you mind clicking the close button to close this pull
request? We actually don't have the permission to do that.
---
If your project is set up for it, you
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1296
---
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/1325#issuecomment-48282385
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16398/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1325#issuecomment-48282384
Merged build finished.
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1325#issuecomment-48282477
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/1316#issuecomment-48282497
@johnnywalleye mind adding `[MLlib]` to the title. Then it's more likely to
catch @mengxr's eye :)
---
If your project is set up for it, you can reply to this email
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/931#issuecomment-48282671
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/931#issuecomment-48282776
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 have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1325#issuecomment-48282775
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1314#issuecomment-48282767
Definitely we can merge this first. I can submit a PR later to remove
jquery.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1325#issuecomment-48282759
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/931#issuecomment-48282761
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 have
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1244#issuecomment-48283271
LGTM pending tests, this is something that has confused people before, so I
think it's best to just leave it out.
---
If your project is set up for it, you can reply
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1244#issuecomment-48283315
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/1244#issuecomment-48283504
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/1241#issuecomment-48284014
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16396/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-48284602
Merged build finished. All automated tests passed.
---
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/1112#issuecomment-48284603
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16397/
---
If your
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/1069#issuecomment-48285811
@srowen If so, I close the PR and I will submit a new PR meets you said.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user witgo closed the pull request at:
https://github.com/apache/spark/pull/1069
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/1039#issuecomment-48286947
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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1039#issuecomment-48286964
Hey @GregOwen this has fallen out of date, mind updating it? I'd like to
get it merged soon.
---
If your project is set up for it, you can reply to this email and have
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1039#discussion_r14642636
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDD.scala ---
@@ -1235,11 +1235,43 @@ abstract class RDD[T: ClassTag](
/** A description of
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1039#discussion_r14642705
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDD.scala ---
@@ -1235,11 +1235,43 @@ abstract class RDD[T: ClassTag](
/** A description of
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/1069#issuecomment-48287243
@witgo Go ahead. Right now I actually don't see any warnings appear when
the compiler flag is removed, so it looks like all other warnings are
suppressed locally already.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1039#issuecomment-48287316
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 have
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1039#discussion_r14642773
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDD.scala ---
@@ -1235,11 +1235,43 @@ abstract class RDD[T: ClassTag](
/** A description of
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1039#issuecomment-48287336
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 have this
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1039#discussion_r14642790
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDD.scala ---
@@ -1235,11 +1235,43 @@ abstract class RDD[T: ClassTag](
/** A description of
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1039#issuecomment-48287559
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16402/
---
If your project is set up for it, you can
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1039#discussion_r14642874
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDD.scala ---
@@ -1235,11 +1235,43 @@ abstract class RDD[T: ClassTag](
/** A description of
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1039#discussion_r14642915
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDD.scala ---
@@ -1235,11 +1235,43 @@ abstract class RDD[T: ClassTag](
/** A description of
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1039#discussion_r14642925
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDD.scala ---
@@ -1235,11 +1235,43 @@ abstract class RDD[T: ClassTag](
/** A description of
GitHub user jerryshao opened a pull request:
https://github.com/apache/spark/pull/1327
[SPARK-2402] Update the initial position when reuse DiskBlockObjectWriter
Minor fix, `initialPosition` can not be updated after `close()` and
re`open()`, which will lead to error when reusing
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1327#issuecomment-48289644
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/1327#issuecomment-48289657
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 avulanov commented on the pull request:
https://github.com/apache/spark/pull/1155#issuecomment-48290945
@mengxr Thanks! I've addressed all your comments.
Btw., I'm working on one-vs-all decomposition for multi-label training and
hope to share the code in near
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1155#issuecomment-48291038
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/1155#issuecomment-48291055
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/1325#issuecomment-48291669
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16399/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1325#issuecomment-48291668
Merged build finished. All automated tests passed.
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/906#issuecomment-48292618
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/906#issuecomment-48292958
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/906#issuecomment-48292980
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/931#issuecomment-48298665
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16400/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1244#issuecomment-48298659
Merged build finished.
---
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/1244#issuecomment-48298667
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16401/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/931#issuecomment-48298656
Build finished.
---
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/1327#issuecomment-48301689
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16403/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1327#issuecomment-48301683
Merged build finished. All automated tests passed.
---
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/1155#issuecomment-48318580
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16404/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1155#issuecomment-48318579
Merged build finished. All automated tests passed.
---
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/906#issuecomment-48320871
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16405/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/906#issuecomment-48320869
Merged build finished.
---
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/906#issuecomment-48321427
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/906#issuecomment-48321419
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/906#issuecomment-48324832
Merged build finished. All automated tests passed.
---
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/906#issuecomment-48324834
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16406/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1323#issuecomment-48326263
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 lirui-intel opened a pull request:
https://github.com/apache/spark/pull/1328
SPARK-2387: remove stage barrier
This PR is a PoC implementation of
[SPARK-2387](https://issues.apache.org/jira/browse/SPARK-2387).
When a ShuffleMapTask finishes, DAGScheduler will
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1323#issuecomment-48326270
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 willb commented on the pull request:
https://github.com/apache/spark/pull/1323#issuecomment-48326403
@rxin Done; I also updated the comment to reflect the narrower focus after
eliminating overlap with #1153. Thanks!
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1328#issuecomment-48326594
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 johnnywalleye commented on the pull request:
https://github.com/apache/spark/pull/1316#issuecomment-48326815
Sure, 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 not have this
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/1327#issuecomment-48329176
It is alright if this class is not reopen supported, but seems there is not
obvious fence to defend user to reuse this object, so at least this
modification will not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1323#issuecomment-48329998
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16407/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1323#issuecomment-48329997
Merged build finished. All automated tests passed.
---
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 darabos opened a pull request:
https://github.com/apache/spark/pull/1329
[SPARK-2403] Catch all errors during serialization in DAGScheduler
https://issues.apache.org/jira/browse/SPARK-2403
Spark hangs for us whenever we forget to register a class with Kryo. This
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1329#issuecomment-48333968
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 baishuo commented on the pull request:
https://github.com/apache/spark/pull/1312#issuecomment-48352678
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 sarutak closed the pull request at:
https://github.com/apache/spark/pull/604
---
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
1 - 100 of 410 matches
Mail list logo
