GitHub user techaddict opened a pull request:

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

    [SPARK-18366][PYSPARK] Add handleInvalid to Pyspark for QuantileDiscretizer 
and Bucketizer

    ## What changes were proposed in this pull request?
    added the new handleInvalid param for these transformers to Python to 
maintain API parity.
    
    ## How was this patch tested?
    existing tests

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

    $ git pull https://github.com/techaddict/spark SPARK-18366

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

    https://github.com/apache/spark/pull/15817.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 #15817
    
----
commit 0e41b36493fcb5eee5f342f694b0d2bc2a1e6c41
Author: Sandeep Singh <[email protected]>
Date:   2016-11-09T00:03:21Z

    add handleInvalid to QuantileDiscretizer

commit 3b5133cac34dc42db71fabbf12c0a8e44d0fb2ba
Author: Sandeep Singh <[email protected]>
Date:   2016-11-09T00:09:13Z

    fix lint issues

commit 20bfd9b3e1028e54619a992a4b333b4fe8c694bc
Author: Sandeep Singh <[email protected]>
Date:   2016-11-09T00:15:10Z

    handleInvalid to Bucketizer

commit 19224724350a6d6c1936b496784131309ce286b0
Author: Sandeep Singh <[email protected]>
Date:   2016-11-09T00:15:52Z

    fix lint error

commit b4720aa49eb94092aa255dcaa47f3e52b44cd6d2
Author: Sandeep Singh <[email protected]>
Date:   2016-11-09T00:21:04Z

    Merge branch 'master' into SPARK-18366

----


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