GitHub user jkbradley opened a pull request:

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

    [SPARK-7000] [ml] Refactor prediction and tree abstractions to be under 
ml.prediction subpackage

    From JIRA:
    > spark.ml prediction abstractions are currently not gathered; they are in 
both ml.impl and ml.tree.  Instead, they should be gathered into ml.prediction. 
 This will become more important as more abstractions, such as ensembles, are 
added.
    
    I refactored using IntelliJ.
    
    The only additional changes I made were:
    * Better doc for DecisionTreeExample to warn users that it can require more 
memory than run-example provides.
    * line 120 of treeParams.scala (a small correction for a warning)
    
    CC: @mengxr

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

    $ git pull https://github.com/jkbradley/spark dt-api-dt3

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

    https://github.com/apache/spark/pull/5585.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 #5585
    
----
commit 775cecf3b56bab8c665ae431e42acf01891c45a1
Author: Joseph K. Bradley <[email protected]>
Date:   2015-04-19T22:19:37Z

    Refactored prediction and tree abstractions to be under ml.prediction 
sub-package

commit b2cb6ad8651b56e7ad5f33c84bafb2388ccb8a0c
Author: Joseph K. Bradley <[email protected]>
Date:   2015-04-20T03:24:48Z

    Fixed build issues after refactor, and improved doc for DecisionTreeExample

----


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