-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-14472][PYSPARK][ML] Cleanup ML JavaWrapper and related class hierarchy #12304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SPARK-14472][PYSPARK][ML] Cleanup ML JavaWrapper and related class hierarchy #12304
Conversation
… _java_obj and creating Java objects
…Params and JavaCallable to JavaWrapper
|
@jkbradley I noticed a couple of potential issues with current JavaCallable that I took care of here. First, trying to detach the Java object on |
|
Test build #55532 has finished for PR 12304 at commit
|
|
Thanks for the PR. This reorg looks fine. I agree with what you said about del and active_spark_context. My main request is that "JavaWrapperParams" be renamed to "JavaParams" to match JavaModel, JavaEstimator, etc. Also, in util.py lines 102, 181: Update "JavaWrapper" to "JavaParams" in comments |
|
I was thinking that the other classes, like |
|
I made that change and fixed the comments in util.py |
|
Test build #55661 has finished for PR 12304 at commit
|
|
Test build #55665 has finished for PR 12304 at commit
|
|
LGTM |
Currently, JavaWrapper is only a wrapper class for pipeline classes that have Params and JavaCallable is a separate mixin that provides methods to make Java calls. This change simplifies the class structure and to define the Java wrapper in a plain base class along with methods to make Java calls. Also, renames Java wrapper classes to better reflect their purpose.
Ran existing Python ml tests and generated documentation to test this change.