You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Joseph K. Bradley (JIRA)" <ji...@apache.org> on 2016/03/17 18:17:33 UTC

[jira] [Resolved] (SPARK-13937) PySpark ML JavaWrapper, variable _java_obj should not be static

     [ https://issues.apache.org/jira/browse/SPARK-13937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joseph K. Bradley resolved SPARK-13937.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0

Issue resolved by pull request 11767
[https://github.com/apache/spark/pull/11767]

> PySpark ML JavaWrapper, variable _java_obj should not be static
> ---------------------------------------------------------------
>
>                 Key: SPARK-13937
>                 URL: https://issues.apache.org/jira/browse/SPARK-13937
>             Project: Spark
>          Issue Type: Bug
>          Components: ML, PySpark
>            Reporter: Bryan Cutler
>            Assignee: Bryan Cutler
>            Priority: Trivial
>             Fix For: 2.0.0
>
>
> In PySpark ML wrapper.py, the abstract class {{JavaWrapper}} has a static variable {{_java_obj}}.  This is meant to hold an instance of a companion Java object.  It seems as though it was made static accidentally because it is never used, and all assignments done in derived classes are done to a member variable with {{self._java_obj}}.  This does not cause any problems with the current functionality, but it should be changed so as not to cause any confusion and misuse in the future.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org