-
- Downloads
[SPARK-16348][ML][MLLIB][PYTHON] Use full classpaths for pyspark ML JVM calls
## What changes were proposed in this pull request? Issue: Omitting the full classpath can cause problems when calling JVM methods or classes from pyspark. This PR: Changed all uses of jvm.X in pyspark.ml and pyspark.mllib to use full classpath for X ## How was this patch tested? Existing unit tests. Manual testing in an environment where this was an issue. Author: Joseph K. Bradley <joseph@databricks.com> Closes #14023 from jkbradley/SPARK-16348.
Showing
- python/pyspark/ml/common.py 5 additions, 5 deletionspython/pyspark/ml/common.py
- python/pyspark/ml/tests.py 4 additions, 4 deletionspython/pyspark/ml/tests.py
- python/pyspark/mllib/clustering.py 3 additions, 2 deletionspython/pyspark/mllib/clustering.py
- python/pyspark/mllib/common.py 5 additions, 5 deletionspython/pyspark/mllib/common.py
- python/pyspark/mllib/feature.py 1 addition, 1 deletionpython/pyspark/mllib/feature.py
- python/pyspark/mllib/fpm.py 1 addition, 1 deletionpython/pyspark/mllib/fpm.py
- python/pyspark/mllib/recommendation.py 1 addition, 1 deletionpython/pyspark/mllib/recommendation.py
- python/pyspark/mllib/tests.py 8 additions, 7 deletionspython/pyspark/mllib/tests.py
Loading
Please register or sign in to comment