Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[data visualizer import] detect formats on nested json #55616

Open
blookot opened this issue Apr 22, 2020 · 1 comment
Open

[data visualizer import] detect formats on nested json #55616

blookot opened this issue Apr 22, 2020 · 1 comment
Labels
:ml Machine learning

Comments

@blookot
Copy link

blookot commented Apr 22, 2020

Describe the feature: when i use the file import (from data visualizer) on a json having nested fields, i would like all nested fields to be identified as well as their format.
@blookot blookot added the :ml Machine learning label Apr 22, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core (:ml)

droberts195 added a commit to droberts195/elasticsearch that referenced this issue Sep 9, 2020
@droberts195
[ML] Include the "properties" layer in find_file_structure mappings
6ddd910 
Previously the "mappings" field of the response from the
find_file_structure endpoint was not a drop-in for the
mappings format of the create index endpoint - the
"properties" layer was missing.  The reason for omitting
it initially was that the assumption was that the
find_file_structure endpoint would only ever return very
simple mappings without any nested objects.  However,
this will not be true in the future, as we will improve
mappings detection for complex JSON objects.  As a first
step it makes sense to move the returned mappings closer
to the standard format.

This is a small building block towards fixing elastic#55616
@droberts195 droberts195 mentioned this issue Sep 9, 2020
Merged
droberts195 added a commit that referenced this issue Sep 9, 2020
@droberts195
[ML] Include the "properties" layer in find_file_structure mappings (#…
6008a74 
…62158)

Previously the "mappings" field of the response from the
find_file_structure endpoint was not a drop-in for the
mappings format of the create index endpoint - the
"properties" layer was missing.  The reason for omitting
it initially was that the assumption was that the
find_file_structure endpoint would only ever return very
simple mappings without any nested objects.  However,
this will not be true in the future, as we will improve
mappings detection for complex JSON objects.  As a first
step it makes sense to move the returned mappings closer
to the standard format.

This is a small building block towards fixing #55616
droberts195 added a commit that referenced this issue Sep 10, 2020
@droberts195
[ML] Include the "properties" layer in find_file_structure mappings (#…
969a1c5 
…62158)

Previously the "mappings" field of the response from the
find_file_structure endpoint was not a drop-in for the
mappings format of the create index endpoint - the
"properties" layer was missing.  The reason for omitting
it initially was that the assumption was that the
find_file_structure endpoint would only ever return very
simple mappings without any nested objects.  However,
this will not be true in the future, as we will improve
mappings detection for complex JSON objects.  As a first
step it makes sense to move the returned mappings closer
to the standard format.

This is a small building block towards fixing #55616
@droberts195 droberts195 mentioned this issue Mar 17, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:ml Machine learning
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@elasticmachine @blookot