-
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-17173][SPARKR] R MLlib refactor, cleanup, reformat, fix deprecation in test #14735
Conversation
Test build #64150 has finished for PR 14735 at commit
|
Test build #64151 has finished for PR 14735 at commit
|
Test build #64154 has finished for PR 14735 at commit
|
This seems a big enough change that it might be good to have a JIRA for this ? |
This also tighten the signature for mllib by removing the previously unused
|
Test build #64157 has finished for PR 14735 at commit
|
* checking S3 generic/method consistency ... WARNING print: function(x, ...) print.summary.GeneralizedLinearRegressionModel: function(x) print: function(x, ...) print.summary.GeneralizedLinearRegressionModel: function(x)
Test build #64161 has finished for PR 14735 at commit
|
@junyangq Could you help review this PR? |
return(list(coefficients = coefficients, size = size, | ||
cluster = cluster, is.loaded = is.loaded)) | ||
list(coefficients = coefficients, size = size, | ||
cluster = cluster, is.loaded = is.loaded) |
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.
align list arguments?
Test build #64198 has finished for PR 14735 at commit
|
any more thought? I'd like to merge to facilitate more R mllib work. |
LGTM |
@felixcheung I didn't look at the code very closely, but will this change be required in |
I don't think they should be required for branch 2.0 - some part of the signature change with ... is likely good to have for consistency but those might also be "breaking" for a *.0.1 release If we think we should - since we did make some changes like that in 2.0.0 branch - I could open a PR for the branch separately. |
Leaving it out of branch-2.0 sounds good to me. |
What changes were proposed in this pull request?
refactor, cleanup, reformat, fix deprecation in test
How was this patch tested?
unit tests, manual tests