GitHub user HyukjinKwon opened a pull request:

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

    [SPARK-14615][ML][FOLLOWUP] Fix Python examples to use the new ML Vector 
and Matrix APIs in the ML pipeline based algorithms

    ## What changes were proposed in this pull request?
    
    This PR fixes Python examples to use the new ML Vector and Matrix APIs in 
the ML pipeline based algorithms.
    
    I firstly executed this shell command, `grep -r "from pyspark.mllib" .` and 
then executed them all.
    Some of tests in `ml` produced the error messages as below:
    
    ```
    pyspark.sql.utils.IllegalArgumentException: u'requirement failed: Input 
type must be VectorUDT but got 
org.apache.spark.mllib.linalg.VectorUDT@f71b0bce.'
    ```
    
    So, I fixed them to use new ones just identically with some Python tests 
fixed in https://github.com/apache/spark/pull/12627
    
    ## How was this patch tested?
    
    Manually tested for all the examples listed by `grep -r "from 
pyspark.mllib" .`.


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

    $ git pull https://github.com/HyukjinKwon/spark SPARK-14615

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

    https://github.com/apache/spark/pull/13393.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 #13393
    
----
commit 0ddb1f40c0be65dea3fa6372c40fed026eb0ff7c
Author: hyukjinkwon <[email protected]>
Date:   2016-05-29T10:22:21Z

    Fix Python examples

----


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