Skip to content

Conversation

@wojtek-szymanski
Copy link
Contributor

What changes were proposed in this pull request?

Docs for Bucketizer.handleInvalid has 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.

@wojtek-szymanski wojtek-szymanski changed the title [SPARK-19741][ML] Bucketizer.handleInvalid docs improved [SPARK-19714][ML] Bucketizer.handleInvalid docs improved Mar 5, 2017
* 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.
Copy link
Contributor

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

Copy link
Contributor

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

Copy link
Contributor Author

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.

@MLnick
Copy link
Contributor

MLnick commented Mar 6, 2017

ok to test

@SparkQA
Copy link

SparkQA commented Mar 6, 2017

Test build #74008 has finished for PR 17169 at commit 13e0245.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@SparkQA
Copy link

SparkQA commented Mar 6, 2017

Test build #74041 has finished for PR 17169 at commit ca6e957.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Can one of the admins verify this patch?

@srowen
Copy link
Member

srowen commented Jul 27, 2018

@wojtek-szymanski if you'll rebase this I'll merge it.

@wangyum
Copy link
Member

wangyum commented Nov 10, 2018

@srowen
Copy link
Member

srowen commented Nov 10, 2018

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

@asfgit asfgit closed this in a3ba3a8 Nov 11, 2018
asfgit pushed a commit that referenced this pull request Nov 11, 2018
## 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]>
jackylee-ch pushed a commit to jackylee-ch/spark that referenced this pull request Feb 18, 2019
## 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]>
zifeif2 pushed a commit to zifeif2/spark that referenced this pull request Nov 22, 2025
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants