You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a meta issue to keep track of moving all components (the API endpoints as well the file and index based visualizers) of the Data Visualizer from the ml plugin into its own separate plugins file_upload and data_visualizer.
This is a meta issue to keep track of moving all components (the API endpoints as well the file and index based visualizers) of the Data Visualizer from the
ml
plugin into its own separate pluginsfile_upload
anddata_visualizer
.file_data_visualizer/import
route tofile_upload
plugin [ml] migrate file_data_visualizer/import route to file_upload plugin #89640 (v7.12)file_data_visualizer/analyze_file
tofile_upload
plugin [ml] migrate file_data_visualizer/analyze_file to file_upload plugin #94259 (v7.13)file_data_visualizer
plugin [ML] Moving file data vizualizer to its own plugin #96408 (v7.13)index_exists
andtime_field_range
endpoints to thefileUpload
plugin to assist with importing data (v7.13)analyze_file
endpoint fromfileUpload
tofileDataVisualizer
(v7.13)View in Data Visualizer
card after file import is successfulfile_data_visualizer
plugin [ML] Move the index data visualizer into a separate plugin #98939get_overall_stats
andget_field_stats
routes and services to internal/data_visualizerIIndexPattern
withIndexPattern
and replace deprecatedIFieldType
withIndexPatternField
RuntimeMappings
withestypes.RuntimeFields
Could be done by adding a common category to each link.
Will be hard to implement because we don't know how many links there will be.
React.lazy
rather than these custom lazy loaders (original comment)The text was updated successfully, but these errors were encountered: