[ML] adds support for non-numeric mapped types#40220
Merged
benwtrent merged 7 commits intoelastic:masterfrom Mar 22, 2019
Merged
[ML] adds support for non-numeric mapped types#40220benwtrent merged 7 commits intoelastic:masterfrom
benwtrent merged 7 commits intoelastic:masterfrom
Conversation
Collaborator
|
Pinging @elastic/ml-core |
a961460 to
00c70b8
Compare
Member
Author
|
run elasticsearch-ci/packaging-sample |
davidkyle
approved these changes
Mar 21, 2019
| e); | ||
| }), latch)); | ||
| try { | ||
| latch.await(LOAD_TRANSFORM_TIMEOUT_IN_SECONDS, TimeUnit.SECONDS); |
Member
There was a problem hiding this comment.
TIL: I thought fieldMappings would have to be volatile for the assignment to be visible to the awaiting thread but latch.await is a synchronisation point. https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/package-summary.html#MemoryVisibility.
I presume we are blocking here because super.maybeTriggerAsyncJob(now); must execute on the calling thread.
Member
Author
|
run elasticsearch-ci/bwc |
|
run elasticsearch-ci/1 |
Member
Author
|
run elasticsearch-ci/packaging-sample |
Contributor
|
does this title need amending? |
benwtrent
added a commit
to benwtrent/elasticsearch
that referenced
this pull request
Mar 22, 2019
* [ML] adds support for non-numeric mapped types and mapping overrides * correcting hlrc compilation issues after merge * removing mapping_override option * clearing up unnecessary changes
jasontedor
added a commit
to jasontedor/elasticsearch
that referenced
this pull request
Mar 22, 2019
* elastic/master: [DOCS] Adds notable highlights tags (elastic#40330) [ML] making test more determinate (elastic#40374) [ML] adds support for non-numeric mapped types (elastic#40220) Move outbound message handling to OutboundHandler (elastic#40336) Add implicit this for class binding in Painless (elastic#40285) Muting test testExtractIndexCheckpointsInconsistentGlobalCheckpoints (elastic#40371) DOC: polish client docs Fix building bwc versions (elastic#40361)
jasontedor
added a commit
to jasontedor/elasticsearch
that referenced
this pull request
Mar 22, 2019
…-stop-time * elastic/master: [DOCS] Adds notable highlights tags (elastic#40330) [ML] making test more determinate (elastic#40374) [ML] adds support for non-numeric mapped types (elastic#40220) Move outbound message handling to OutboundHandler (elastic#40336) Add implicit this for class binding in Painless (elastic#40285)
benwtrent
added a commit
that referenced
this pull request
Mar 23, 2019
This file contains hidden or 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
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.
This PR does a handful of things to address the issues when creating the destination index mapping and parsing the resulting aggregations before indexing them.
The destination mapping type is taken into account now when extracting the data before putting it into the destination index. Right now all that is considered if the destination is a
Numerictype or not, but this should not restrict more complex type requirements in the future (if they should arise).Future work:
fieldsmapping overrides. This should be added in tandem with our support of such in mapping deduction. Not added in this PR.bucket_script) do not provide interfaces to accurately determine the resultant type. For this scenario the end user should provide some sort of mapping type for the field result.Alternative designs:
getValueAsString_sourceas strings. This could lead to confusion, especially when considering our_previewendpoint.getValueAsStringthrough Java type parsingintegeris actually akeyword.closes #39974