[SPARK-21388][ML][PySpark] GBTs inherit from HasStepSize & LInearSVC from HasThreshold#18612
[SPARK-21388][ML][PySpark] GBTs inherit from HasStepSize & LInearSVC from HasThreshold#18612zhengruifeng wants to merge 5 commits intoapache:masterfrom
Conversation
|
Test build #79557 has finished for PR 18612 at commit
|
|
Test build #79560 has finished for PR 18612 at commit
|
There was a problem hiding this comment.
Maybe the error can be eliminated after removing this line, and actually we should set default value in the concrete class if it's inherited.
|
Test build #79652 has finished for PR 18612 at commit
|
|
So improving the doc certainly makes sense on the Python side (thank you for catching that). But as @MLnick asked on the JIRA - I'm not super sure I see the point of the refactor on the Scala side. If we have a parameter with the same name but a different meaning why mix in a base trait only to override its only meaningful provided value? What do you think @jkbradley? |
|
@holdenk I think the meaning of |
|
It makes sense for As for GBT, well I am sort of indifferent as the step size is roughly analogous between the two definitions (in both cases it is a learning rate). |
|
Test build #79897 has finished for PR 18612 at commit
|
python/pyspark/ml/feature.py
Outdated
There was a problem hiding this comment.
This also needs to be reverted.
| kwargs = self._input_kwargs | ||
| return self._set(**kwargs) | ||
|
|
||
| @since("1.4.0") |
There was a problem hiding this comment.
and similarly here, added back
|
Test build #80001 has finished for PR 18612 at commit
|
|
Merged into master, thanks for all. |
What changes were proposed in this pull request?
GBTs inherit from HasStepSize & LInearSVC/Binarizer from HasThreshold
How was this patch tested?
existing tests