GitHub user freeman-lab opened a pull request:

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

    [SPARK-3128][MLLIB] Use streaming test suite for StreamingLR

    Refactored tests for streaming linear regression to use existing  streaming 
test utilities. Summary of changes:
    - Made ``mllib`` depend on tests from ``streaming``
    - Rewrote prediction and convergence tests to use ``setupStreams`` and 
``runStreams``
    - Added new test for the accuracy of predictions generated by 
``predictOnValue``
    
    These tests should run faster, be easier to extend/maintain, and provide a 
reference for new tests.
    
    @mengxr @tdas

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

    $ git pull https://github.com/freeman-lab/spark streamingLR-predict-tests

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

    https://github.com/apache/spark/pull/2037.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 #2037
    
----
commit 32c43c2928868505a3af3a79db8e25a494a7c09a
Author: freeman <[email protected]>
Date:   2014-08-19T02:25:38Z

    Added test for prediction
    
    - Test predictOnValues for accuracy on a test stream

commit 50eb0bfcf59b8fc3f8ab7b441eb3cbbf46299e1f
Author: freeman <[email protected]>
Date:   2014-08-19T16:53:46Z

    Refactored tests to use streaming test tools
    
    - Made mllib depend on tests from streaming
    - Rewrote all streamingLR tests to use the setupStreams & runStreams
    functions

----


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