GitHub user BenFradet opened a pull request:

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

    [SPARK-9716] [ML] BinaryClassificationEvaluator should accept Double 
prediction column

    This PR aims to allow the prediction column of 
`BinaryClassificationEvaluator` to be of double type.

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

    $ git pull https://github.com/BenFradet/spark SPARK-9716

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

    https://github.com/apache/spark/pull/10472.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 #10472
    
----
commit 2c427752ae28e512d3f076a14f46527946f27012
Author: BenFradet <[email protected]>
Date:   2015-12-23T22:38:12Z

    new checkColumnType method checking for a variety of types

commit df58edc76e4b4c84ace4a7b3962e3175c4a5bfab
Author: BenFradet <[email protected]>
Date:   2015-12-23T22:38:39Z

    binary classification evaluator now accepts raw prediction col of type 
vector and double

commit 8e80dfade54c81e7d951643aa67cc376665d8339
Author: BenFradet <[email protected]>
Date:   2015-12-24T22:09:27Z

    removed overload disambiguation

commit 80fde3f9b6e124c80a7d5a2ee2a0363fdc216448
Author: BenFradet <[email protected]>
Date:   2015-12-24T23:23:07Z

    binary classification evaluator evaluate method now handles both vector and 
double types

commit 725f6a5931ac763e9ca1fa0d9a9c590d6887900d
Author: BenFradet <[email protected]>
Date:   2015-12-24T23:23:18Z

    test suite

----


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