Github user anantasty commented on the pull request:
https://github.com/apache/spark/pull/2952#issuecomment-61316422
The URL shows 0 failures I am not sure why it says the tests fail.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user anantasty commented on the pull request:
https://github.com/apache/spark/pull/2952#issuecomment-61305691
@mengxr @davies Thanks for the time and guidance
---
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 anantasty commented on a diff in the pull request:
https://github.com/apache/spark/pull/2952#discussion_r19683664
--- Diff: examples/src/main/python/mllib/word2vec.py ---
@@ -0,0 +1,50 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
Github user anantasty commented on the pull request:
https://github.com/apache/spark/pull/2970#issuecomment-61222188
@marmbrus can we merge this 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 your project does
Github user anantasty commented on the pull request:
https://github.com/apache/spark/pull/2952#issuecomment-61222153
@davies @mengxr Just made the suggested changes.
---
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 anantasty commented on a diff in the pull request:
https://github.com/apache/spark/pull/2952#discussion_r19653043
--- Diff: examples/src/main/python/mllib/word2vec.py ---
@@ -0,0 +1,48 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
Github user anantasty commented on a diff in the pull request:
https://github.com/apache/spark/pull/2952#discussion_r19585598
--- Diff: docs/mllib-feature-extraction.md ---
@@ -162,6 +162,40 @@ for((synonym, cosineSimilarity) <- synonyms) {
}
{% endhighli
Github user anantasty commented on a diff in the pull request:
https://github.com/apache/spark/pull/2952#discussion_r19585582
--- Diff: examples/src/main/python/mllib/word2vec.py ---
@@ -0,0 +1,48 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
Github user anantasty commented on the pull request:
https://github.com/apache/spark/pull/2970#issuecomment-60877768
@marmbrus just did that. Thanks for that.
---
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 anantasty commented on the pull request:
https://github.com/apache/spark/pull/2942#issuecomment-60795596
I would certainly be interested in doing that. I just wasn't sure if it was
better to do it as a separate PR/ task.
On Oct 28, 2014 11:19 AM, "Xia
Github user anantasty commented on the pull request:
https://github.com/apache/spark/pull/2970#issuecomment-60753209
Thanks @liancheng. I will keep that in mind
---
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 anantasty commented on the pull request:
https://github.com/apache/spark/pull/2952#issuecomment-60710266
@mengxr I just implemented those changes.
I kept the command line args very simple instead of using arg parse etc
just for the sake of simplicity.
Thanks for
Github user anantasty commented on the pull request:
https://github.com/apache/spark/pull/2970#issuecomment-60708775
This fixes https://issues.apache.org/jira/browse/SPARK-4108
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
GitHub user anantasty opened a pull request:
https://github.com/apache/spark/pull/2970
[SPARK-4108][sql]
Fixed usage of deprecated in sql/catalyst/types/datatypes to have
versio...n parameter
You can merge this pull request into a Git repository by running:
$ git pull https
Github user anantasty commented on the pull request:
https://github.com/apache/spark/pull/2952#issuecomment-60687518
@mengxr I updated the example code as well.
---
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 anantasty commented on the pull request:
https://github.com/apache/spark/pull/2942#issuecomment-60554980
Should we create another PR for the python bindings/example?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
GitHub user anantasty opened a pull request:
https://github.com/apache/spark/pull/2952
[examples][mllib][python] SPARK-3838
This pull request refers to issue:
https://issues.apache.org/jira/browse/SPARK-3838
Python example for word2vec
You can merge this pull request into
GitHub user anantasty opened a pull request:
https://github.com/apache/spark/pull/2948
Just fixing comment that shows usage
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/anantasty/spark patch-1
Alternatively you can review
Github user anantasty closed the pull request at:
https://github.com/apache/spark/pull/2582
---
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 anantasty opened a pull request:
https://github.com/apache/spark/pull/2582
Changed the linke to build spark
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/anantasty/spark readme_build_instr
Alternatively you can
Github user anantasty commented on a diff in the pull request:
https://github.com/apache/spark/pull/2451#discussion_r17802806
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/optimization/Gradient.scala ---
@@ -157,3 +157,221 @@ class HingeGradient extends Gradient
Github user anantasty commented on a diff in the pull request:
https://github.com/apache/spark/pull/2451#discussion_r17802195
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/linalg/Matrices.scala
---
@@ -17,12 +17,19 @@
package org.apache.spark.mllib.linalg
Github user anantasty commented on a diff in the pull request:
https://github.com/apache/spark/pull/2451#discussion_r17801907
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/linalg/BLAS.scala ---
@@ -197,4 +201,452 @@ private[mllib] object BLAS extends Serializable
Github user anantasty commented on the pull request:
https://github.com/apache/spark/pull/2451#issuecomment-56217049
@brkyvz I will get on it
---
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 anantasty commented on the pull request:
https://github.com/apache/spark/pull/2451#issuecomment-56108815
With some guidance I could help you with the docs
---
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 anantasty commented on the pull request:
https://github.com/apache/spark/pull/941#issuecomment-46361287
@pwendell Ouch! my bad. Thanks for the 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
Github user anantasty commented on the pull request:
https://github.com/apache/spark/pull/941#issuecomment-46057116
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 anantasty commented on the pull request:
https://github.com/apache/spark/pull/1062#issuecomment-45977149
@pwendell I can certianly do that.
---
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 anantasty opened a pull request:
https://github.com/apache/spark/pull/1062
Made splits deprecated in JavaRDDLike
The jira for the issue can be found at:
https://issues.apache.org/jira/browse/SPARK-2061
Most of spark has used over to consistently using `partitions
Github user anantasty commented on the pull request:
https://github.com/apache/spark/pull/941#issuecomment-45681313
I just created _check_output within the module. Fixes the issue in python
2.6 and 2.7
---
If your project is set up for it, you can reply to this email and have your
Github user anantasty commented on the pull request:
https://github.com/apache/spark/pull/941#issuecomment-45023956
We could dynamically add the method to subprocess within the scope or
create a function in the scope both of them sound like acceptable solutions
On Jun 3, 2014 2
Github user anantasty commented on the pull request:
https://github.com/apache/spark/pull/941#issuecomment-45018927
That might actually be a smarter idea. We could just extend subprocess to
add check_all and use that.
On Tue, Jun 3, 2014 at 2:43 PM, Patrick Wendell
Github user anantasty commented on the pull request:
https://github.com/apache/spark/pull/941#issuecomment-45008322
Agreed.
On Jun 3, 2014 12:08 PM, "Matei Zaharia" wrote:
> Let's make 2.7 also use Popen then. It seems unnecessary to have two code
&g
Github user anantasty commented on the pull request:
https://github.com/apache/spark/pull/941#issuecomment-44910621
Popen is the old way to do it. You could capture the stderror if you want
or just let it raise (default behavior). check_output is more pythonic since
python 2.7. 2.6
GitHub user anantasty opened a pull request:
https://github.com/apache/spark/pull/941
added compatibility for python 2.6 for ssh_read command
https://issues.apache.org/jira/browse/SPARK-1990
You can merge this pull request into a Git repository by running:
$ git pull https
35 matches
Mail list logo
