-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-19714][ML] Bucketizer.handleInvalid docs improved #17169
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
Conversation
| * Param for how to handle invalid entries. Options are 'skip' (filter out rows with | ||
| * invalid values), 'error' (throw an error), or 'keep' (keep invalid values in a special | ||
| * additional bucket). | ||
| * Param for how to handle invalid entries containing either NaN or null values. |
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.
This is actually not true currently - null is not handled as an invalid value - see https://issues.apache.org/jira/browse/SPARK-19781
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 once #17123 maybe merged it will hold true
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.
You are right. I will update docs with null values support once #17123 gets merged.
|
ok to test |
|
Test build #74008 has finished for PR 17169 at commit
|
|
Test build #74041 has finished for PR 17169 at commit
|
|
Can one of the admins verify this patch? |
|
@wojtek-szymanski if you'll rebase this I'll merge it. |
|
True, though the sentence that is added in this PR isn't added. I can just add it to close the loop here. This PR can be closed , as it seems abandoned |
## What changes were proposed in this pull request? Clarify Bucketizer handleInvalid docs. Just a resubmit of #17169 ## How was this patch tested? N/A Closes #23003 from srowen/SPARK-19714. Authored-by: Sean Owen <[email protected]> Signed-off-by: Sean Owen <[email protected]>
## What changes were proposed in this pull request? Clarify Bucketizer handleInvalid docs. Just a resubmit of apache#17169 ## How was this patch tested? N/A Closes apache#23003 from srowen/SPARK-19714. Authored-by: Sean Owen <[email protected]> Signed-off-by: Sean Owen <[email protected]>
Closes apache#21766 Closes apache#21679 Closes apache#21161 Closes apache#20846 Closes apache#19434 Closes apache#18080 Closes apache#17648 Closes apache#17169 Add: Closes apache#22813 Closes apache#21994 Closes apache#22005 Closes apache#22463 Add: Closes apache#15899 Add: Closes apache#22539 Closes apache#21868 Closes apache#21514 Closes apache#21402 Closes apache#21322 Closes apache#21257 Closes apache#20163 Closes apache#19691 Closes apache#18697 Closes apache#18636 Closes apache#17176 Closes apache#23001 from wangyum/CloseStalePRs. Authored-by: Yuming Wang <[email protected]> Signed-off-by: hyukjinkwon <[email protected]>
What changes were proposed in this pull request?
Docs for
Bucketizer.handleInvalidhas been enhanced with more detailed information about supported and not supported types of invalid entries.How was this patch tested?
N/A, just dosc update.