Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/245#issuecomment-39176037
@mateiz Centering will be available after
https://github.com/apache/spark/pull/268 gets merged.
---
If your project is set up for it, you can reply to this email and have
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/245#discussion_r11149337
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/linalg/Vectors.scala
---
@@ -54,6 +54,12 @@ trait Vector extends Serializable {
* Converts the ins
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/282#issuecomment-39175267
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/282#issuecomment-39175258
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 ha
GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/282
[SQL] SPARK-1372 Support for caching and uncaching tables in a SQLContext.
This doesn't yet support different databases in Hive (though you can
probably workaround this by calling `USE `). However,
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/281
---
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 enabl
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/97#issuecomment-39175081
Hey @mateiz take another look ?
---
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 yinxusen commented on the pull request:
https://github.com/apache/spark/pull/268#issuecomment-39174557
@mengxr Ah... I totally understand your mean. Code is on the way.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/245#issuecomment-39174195
One other thing, for the centering, will we create a utility function for
it later? We should add a JIRA. I agree that they need to be removed by default.
---
If your proj
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/245#discussion_r11148578
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/linalg/Vectors.scala
---
@@ -54,6 +54,12 @@ trait Vector extends Serializable {
* Converts the ins
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/245#issuecomment-39173844
Hey Xiangrui, why have a MLContext at all? Why not just make the input
methods part of MLUtils? This is the pattern we've followed with other input
methods (e.g. KafkaUtils
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/281#issuecomment-39173387
Thanks, merged.
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/279#issuecomment-39173083
@mridulm I resolved the PR as well
https://issues.apache.org/jira/browse/SPARK-1376
---
If your project is set up for it, you can reply to this email and have your
reply
Github user concretevitamin commented on the pull request:
https://github.com/apache/spark/pull/251#issuecomment-39172164
Is this good to go? I can see the argument that `SparkListenerShutdown` is
probably not doing anything now, but removing it should be in another PR. To
stick with
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/281#issuecomment-39170786
@andrewor14 Thanks for the quick fix!
---
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 n
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/280
---
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 enabl
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/280#issuecomment-39170370
Looks like this one involved only very minor changes. So I'm gonna go ahead
and merge this.
---
If your project is set up for it, you can reply to this email and have yo
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-39169881
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13623/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-39169879
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/281#issuecomment-39169389
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/281#issuecomment-39169390
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13622/
---
If your project
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/279
---
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 enabl
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-39167685
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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-39167697
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/281#issuecomment-39167268
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/281#issuecomment-39167276
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/281#issuecomment-39167165
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/281#issuecomment-39165202
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13620/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39165203
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13621/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/281#issuecomment-39165201
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39165200
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/279#issuecomment-39164519
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39164522
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13618/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39164520
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/279#issuecomment-39164521
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13619/
---
If your project
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/279#issuecomment-39163646
@mridulm unfortunately we've encountered a jenkins bug that causes this
message to get printed in two different situations.
---
If your project is set up for it, you can
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/279#issuecomment-39163251
Hmm, looks like the push 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 project does no
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/279#issuecomment-39163056
LGTM, pushed to 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 have this f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39162979
Merged build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear o
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39162969
Merged build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appea
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/245#issuecomment-39162821
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13616/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/245#issuecomment-39162820
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/281#issuecomment-39162517
Merged build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear o
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/281#issuecomment-39162082
Merged build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appea
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/281
[Hot Fix #42] Persisted RDD disappears on storage page if re-used
If a previously persisted RDD is re-used, its information disappears from
the Storage page.
This is because the tasks ass
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39161804
@mateiz Here's a more complete version. Note that this includes the
sql/hql distinction we discussed, but only for Java. I'll do the scala one in
a separate PR.
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/279#issuecomment-39161679
That is a fairly ambiguous message from jenkins :-) cc @pwendell
---
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/279#issuecomment-39161596
Merged build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appea
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/279#issuecomment-39161604
Merged build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear o
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/279#issuecomment-39161560
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39161333
Merged build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear o
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39161317
Merged build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appea
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39161187
Merged build finished. Build is starting -or- tests failed to complete.
---
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/248#issuecomment-39161188
Build is starting -or- tests failed to complete.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13617/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39161060
Merged build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appea
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39161066
Merged build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear o
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/245#issuecomment-39160061
Merged build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear o
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/245#issuecomment-39160051
Merged build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appea
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/246#issuecomment-39159315
Build finished. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/246#issuecomment-39159316
Build is starting -or- tests failed to complete.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13615/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-39159295
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-39159296
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13614/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/246#issuecomment-39159190
Build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/246#issuecomment-39159181
Build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/252#issuecomment-39158673
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/252#issuecomment-39158674
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13611/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39156083
Build is starting -or- tests failed to complete.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13613/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39156082
Merged build finished. Build is starting -or- tests failed to complete.
---
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/79#issuecomment-39155725
Merged build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-39155715
Merged build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/277
---
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 enabl
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39155380
Merged build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appea
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39155385
Merged build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear o
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-39155337
@manishamde Please merge the changes at
https://github.com/manishamde/spark/pull/4
---
If your project is set up for it, you can reply to this email and have your
reply ap
Github user manishamde commented on a diff in the pull request:
https://github.com/apache/spark/pull/79#discussion_r11142394
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/tree/configuration/Strategy.scala
---
@@ -0,0 +1,47 @@
+/*
+ * Licensed to the Apache Software
Github user manishamde commented on a diff in the pull request:
https://github.com/apache/spark/pull/79#discussion_r11142399
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/tree/DecisionTreeSuite.scala ---
@@ -0,0 +1,431 @@
+/*
+ * Licensed to the Apache Software Foun
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39155211
Test failure seems unrelated: `Could not find Apache license headers in the
following files:
!? /root/workspace/SparkPullRequestBuilder/.mima-excludes`
---
If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39155142
Build is starting -or- tests failed to complete.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13612/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39155141
Build finished. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user manishamde commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-39155083
@mengxr I am not sure the merge of your PR on my repo went through. I might
have closed the PR accidentally and I can't find a way to undo it. Could you
please re-send y
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39155070
Build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39155060
Build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-39154884
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-39154885
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13609/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/280#issuecomment-39154661
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/280#issuecomment-39154662
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13608/
---
If your project
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/280#issuecomment-39154274
Yep - that's the reason this is proposing going to 8 instead of 9... :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/280#issuecomment-39154246
(Just in case anyone had the same question I did -- Jetty 8 does indeed
only require Java 6 unlike Jetty 9)
---
If your project is set up for it, you can reply to this ema
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/79#discussion_r11141936
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/tree/DecisionTreeSuite.scala ---
@@ -0,0 +1,431 @@
+/*
+ * Licensed to the Apache Software Foundati
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/79#discussion_r11141895
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/tree/configuration/Strategy.scala
---
@@ -0,0 +1,47 @@
+/*
+ * Licensed to the Apache Software Fou
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-39153779
@manishamde I sent some minor code style updates to your repo. Please take
a look and merge it into this PR. 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/252#issuecomment-39153384
Merged build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appea
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/252#issuecomment-39153392
Merged build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear o
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39152813
Build is starting -or- tests failed to complete.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13610/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39152812
Build finished. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39152681
Build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39152688
Build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/250
---
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 enabl
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/276#issuecomment-39150971
And for EdgeTripletIterator we should just keep your change (i.e. always
create a new row) since that is not used internally at all.
---
If your project is set up for it, y
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/276#issuecomment-39150913
Thanks for sending this in. It's something that is extremely confusing in
graphx and we need to fix it. However, I am not sure if taking out the object
reuse in edges is the
1 - 100 of 214 matches
Mail list logo
