-
Notifications
You must be signed in to change notification settings - Fork 28.5k
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-29656][ML][PYSPARK] ML algs expose aggregationDepth #26322
Conversation
Test build #112920 has finished for PR 26322 at commit
|
@@ -34,7 +34,8 @@ import org.apache.spark.sql.types.{StructField, StructType} | |||
/** | |||
* Params for [[RobustScaler]] and [[RobustScalerModel]]. | |||
*/ | |||
private[feature] trait RobustScalerParams extends Params with HasInputCol with HasOutputCol { | |||
private[feature] trait RobustScalerParams extends Params with HasInputCol with HasOutputCol | |||
with HasAggregationDepth { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess you forgot to put setAggregationDepth
in class RobustScaler
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch! thanks!
Test build #112988 has finished for PR 26322 at commit
|
Test build #112991 has finished for PR 26322 at commit
|
Test build #112996 has finished for PR 26322 at commit
|
Test build #113017 has finished for PR 26322 at commit
|
retest this please |
Test build #113025 has finished for PR 26322 at commit
|
Hm, I am really not sure users can meaningfully tune this, so I'm not sure about adding so much complexity for it. In some cases I think we use reduce vs treeReduce on purpose as it can be faster; it really depends on the usage. |
@srowen Thanks for reviewing! |
Test build #113072 has finished for PR 26322 at commit
|
retest this please |
Test build #113264 has finished for PR 26322 at commit
|
merged to master, thanks all |
Retroactively: OK I understand the argument was consistency. I might have pinged for a confirmation first though as I wasn't in favor of this at first look. |
@srowen Sorry for my careless merge. Should I revert it first? |
I think it's OK if it's for consistency. |
What changes were proposed in this pull request?
expose expert param
aggregationDepth
in algs: GMM/GLRWhy are the changes needed?
SVC/LoR/LiR/AFT had exposed expert param aggregationDepth to end users. It should be nice to expose it in similar algs.
Does this PR introduce any user-facing change?
yes, expose new param
How was this patch tested?
added pytext tests