Github user yanboliang closed the pull request at:
https://github.com/apache/spark/pull/7357
---
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/7357#issuecomment-163701403
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/7357#issuecomment-163701306
**[Test build #47502 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47502/console)**
for PR 7357 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7357#issuecomment-163701402
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 project does
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7357#issuecomment-163649655
[Test build #47502 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47502/consoleFull)
for PR 7357 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/7357#issuecomment-135331297
Yeah, I think the question is, what's the need / motivation? I don't see
this being used in the code. If it's just because it sounds useful, I'm not
sure that's enough
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7357#issuecomment-134918812
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/7357#issuecomment-134918751
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/7357#issuecomment-134934506
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/7357#issuecomment-134934396
[Test build #41616 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41616/console)
for PR 7357 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7357#issuecomment-134919728
[Test build #41616 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41616/consoleFull)
for PR 7357 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7357#issuecomment-134934508
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user feynmanliang commented on the pull request:
https://github.com/apache/spark/pull/7357#issuecomment-135300832
@yanboliang I think there are some [discussions about whether we should
enrich the Vectors
API](https://www.mail-archive.com/user@spark.apache.org/msg35434.html)
Github user Mageswaran1989 commented on a diff in the pull request:
https://github.com/apache/spark/pull/7357#discussion_r38063538
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/linalg/Vectors.scala
---
@@ -692,6 +744,29 @@ class SparseVector @Since(1.0.0) (
14 matches
Mail list logo
