-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[ML] Move the index data visualizer into a separate plugin #98939
Labels
Comments
peteharverson
added
enhancement
New value added to drive a business result
:ml
v7.14.0
labels
Apr 30, 2021
Pinging @elastic/ml-ui (:ml) |
Hey @peteharverson thanks for this. We are looking forward to having this in Discover, where it will continue to add value, have wider adoption, and also drive ML discussions. @andreadelrio this is the issue, related to ours, that we'll need to design a bit around. |
qn895
changed the title
[ML] Move the index data visualizer into a separate plugin
[Meta] Move the index data visualizer into a separate plugin
Jun 4, 2021
qn895
changed the title
[Meta] Move the index data visualizer into a separate plugin
[Meta][ML] Move the index data visualizer into a separate plugin
Jun 4, 2021
qn895
changed the title
[Meta][ML] Move the index data visualizer into a separate plugin
[ML] Move the index data visualizer into a separate plugin
Jun 4, 2021
25 tasks
3 tasks
35 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue to cover the work to move the ML index data visualizer into a separate plugin.
Background
The index data visualizer allows users to view their indices and quickly get an understanding of the fields in their data using top values, maps and other quick views to show metrics and values in the data. It provides a contextual view into indices to show which fields are getting used, how many documents contain those fields, and the number of unique values and distribution in the field.
Apart from being a powerful part of the ML workflow, this tool has wider applications across Kibana, such as in Discover, where it could be added as an additional view into an index - see #97176. In order to facilitate this, the code should be moved out of ML into a separate plugin, in a similar approach as was recently completed for the file data visualizer - see #96408.
Progress
file_data_visualizer
pluginindex_exists
andtime_field_range
endpoints to thefileUpload
plugin to assist with importing dataanalyze_file
endpoint fromfileUpload
tofileDataVisualizer
file_data_visualizer
pluginget_overall_stats
andget_field_stats
routes and services to internal/data_visualizerIIndexPattern
withIndexPattern
and replace deprecatedIFieldType
withIndexPatternField
RuntimeMappings
withestypes.RuntimeFields
The text was updated successfully, but these errors were encountered: