You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "yuhao yang (JIRA)" <ji...@apache.org> on 2015/04/23 13:51:38 UTC

[jira] [Closed] (SPARK-7089) Introduce LDAOptimizer to LDA to improve extensibility

     [ https://issues.apache.org/jira/browse/SPARK-7089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

yuhao yang closed SPARK-7089.
-----------------------------
    Resolution: Duplicate

Sorry for the duplication

> Introduce LDAOptimizer to LDA to improve extensibility
> ------------------------------------------------------
>
>                 Key: SPARK-7089
>                 URL: https://issues.apache.org/jira/browse/SPARK-7089
>             Project: Spark
>          Issue Type: Improvement
>          Components: MLlib
>    Affects Versions: 1.3.1
>            Reporter: yuhao yang
>            Priority: Minor
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> LDA was implemented with extensibility in mind. And with the development of OnlineLDA and Gibbs Sampling, we are collecting more detailed requirements from different algorithms.
> As Joseph Bradley proposed in https://github.com/apache/spark/pull/4807 and with some further discussion, we'd like to adjust the code structure a little to present the common interface and extension point clearly.
> Basically class LDA would be a common entrance for LDA computing. And each LDA object will refer to a LDAOptimizer for the concrete algorithm implementation. Users can customize LDAOptimizer with specific parameters and assign it to LDA.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org