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
mlplugin into its own separate pluginsfile_uploadanddata_visualizer.file_data_visualizer/importroute tofile_uploadplugin [ml] migrate file_data_visualizer/import route to file_upload plugin #89640 (v7.12)file_data_visualizer/analyze_filetofile_uploadplugin [ml] migrate file_data_visualizer/analyze_file to file_upload plugin #94259 (v7.13)file_data_visualizerplugin [ML] Moving file data vizualizer to its own plugin #96408 (v7.13)index_existsandtime_field_rangeendpoints to thefileUploadplugin to assist with importing data (v7.13)analyze_fileendpoint fromfileUploadtofileDataVisualizer(v7.13)View in Data Visualizercard after file import is successfulfile_data_visualizerplugin [ML] Move the index data visualizer into a separate plugin #98939get_overall_statsandget_field_statsroutes and services to internal/data_visualizerIIndexPatternwithIndexPatternand replace deprecatedIFieldTypewithIndexPatternFieldRuntimeMappingswithestypes.RuntimeFieldsCould 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.lazyrather than these custom lazy loaders (original comment)