[ML] Remove special case handling for missing target field for classification #1036
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
droberts195
approved these changes
Mar 4, 2020
|
retest |
The Java change passed an intake build: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+git+push/3204/ So this PR is safe to merge now. |
tveasey
added a commit
to tveasey/ml-cpp-1
that referenced
this pull request
Mar 6, 2020
tveasey
added a commit
that referenced
this pull request
Mar 9, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following on from #1034, we can simplify the handling of missing target field values for classification. Java will supply the missing string value to denote these are missing rather than the empty string.