GitHub user jliwork opened a pull request:
https://github.com/apache/spark/pull/9920
[SPARK-11569] [ML] Fix StringIndexer to handle null value properly
I was having some problem with rebase on
https://github.com/apache/spark/pull/9709, so I had to close that PR and
creating a new pull request with my latest fix.
Thanks to @jkbradley and @holdenk for your comments. I have updated my fix
so that it will allow user to config either to filter out null values or throw
an error with StringIndexer.setHandleInvalid("skip") API. The default is
StringIndexer.setHandleInvalid("error").
Please let me know what you think. Thanks again!
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jliwork/spark SPARK-11569-new
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/9920.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 #9920
----
commit 19de57454cc751074fbbc6e73a3be25f1429e40b
Author: Jia Li <ji...@us.ibm.com>
Date: 2015-11-23T23:05:26Z
fix SPARK-11569 on new branch
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
