GitHub user hhbyyh opened a pull request:

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

    [SPARK-9578] [ML] Stemmer feature transformer

    jira: https://issues.apache.org/jira/browse/SPARK-9578
    
    Classical Porter stemmer, which is implemented referring to scalanlp/chalk
     * 
[[https://github.com/scalanlp/chalk/blob/master/src/main/scala/chalk/text/analyze]].
 
    @jasonbaldridge Let me know if you're interested. 
    
    I compared the following implementations:
    http://tartarus.org/martin/PorterStemmer/scala.txt
    
https://github.com/ifesdjeen/jReadability/blob/master/src/scala/main/com/jreadability/main/Stemmer.scala
    
https://github.com/aztek/porterstemmer/blob/master/src/main/scala/com/github/aztek/porterstemmer/PorterStemmer.scala
    
    
    


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

    $ git pull https://github.com/hhbyyh/spark stem

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

    https://github.com/apache/spark/pull/10272.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 #10272
    
----
commit 857f68d2fd21c97c780e7d04be4e0a666ec9d52d
Author: Yuhao Yang <[email protected]>
Date:   2015-12-12T02:38:30Z

    initial stemmer

commit 211ac04593afb79051287e159261ad06fa4b4464
Author: Yuhao Yang <[email protected]>
Date:   2015-12-12T02:51:45Z

    line fix

commit ddb26da2b3e15a2b433636bfa4c6d4e5877ea96a
Author: Yuhao Yang <[email protected]>
Date:   2015-12-12T03:13:45Z

    case 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 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