GitHub user mengxr opened a pull request:

    https://github.com/apache/spark/pull/3437

    [SPARK-4582][MLLIB] get raw vectors for further processing in Word2Vec

    This is #3309 for the master branch.
    
    e.g. clustering
    
    Author: tkaessmann <[email protected]>
    
    Closes #3309 from tkaessmann/branch-1.2 and squashes the following commits:
    
    e3a3142 [tkaessmann] changes the comment for getVectors
    58d3d83 [tkaessmann] removes sign from comment
    a5be213 [tkaessmann] fixes getVectors to fit code guidelines
    3782fa9 [tkaessmann] get raw vectors for further processing

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mengxr/spark SPARK-4582

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/3437.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3437
    
----
commit 6c666b42c6c4d1f2949783a729ab89c0e354488f
Author: tkaessmann <[email protected]>
Date:   2014-11-25T00:40:19Z

    get raw vectors for further processing in Word2Vec
    
    e.g. clustering
    
    Author: tkaessmann <[email protected]>
    
    Closes #3309 from tkaessmann/branch-1.2 and squashes the following commits:
    
    e3a3142 [tkaessmann] changes the comment for getVectors
    58d3d83 [tkaessmann] removes sign from comment
    a5be213 [tkaessmann] fixes getVectors to fit code guidelines
    3782fa9 [tkaessmann] get raw vectors for further processing

----


---
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 enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to