Search 👉 New Platform

[lukeelmers]

Parent issue #31968
Related to #51560
Blocked by #47644

Summary

This captures the remaining work that needs to be done to prepare and migrate the data search service to the new platform.

courier

• Move ui/courier into the search service of src/legacy/core_plugins/data (Phase I)
  • Audit public contracts Clean up ui/courier exports. #52037
  • Move over files Move ui/courier into data shim plugin #52359

agg_types

• Move ui/agg_types into the search service of src/legacy/core_plugins/data (Phase I)
  • Audit public contracts
  • Move over files Move ui/agg_types in to shim data plugin #56353
  • move agg_response/tabify [ui/agg_response/tabify] -> TypeScript & Jest & Shim #57394
• Shim/Remove remaining legacy dependencies (Phase II) agg_types: Remove legacy dependencies #56934
• clean up static exports
  • also look at dateHistogramInterval & code left in common
• time buckets & setBounds - make static, move into agg types for date_histogram Clean up date histogram agg type. #58805
• remove Schemas removing schemas from agg configs #58462
• Cutover to new platform (Phase III)
• Update dev docs issue Dev Docs entry: ui/public & angular cleanup 7.6 #43511

[elasticmachine]

Pinging @elastic/kibana-app-arch

[lukeelmers]

Just to add a note for folks currently blocked on the search service:

At this point everything should be available in the new platform except ui/agg_types and ui/agg_response/tabify

If you are not relying on either of these items in some way, then you should be able to move forward with migration. Otherwise, this is the right issue to follow along with progress 😄

[lukeelmers]

Closing this issue, as agg_types, tabify, and esaggs were all cut over to the new platform in #59605. At this point any teams relying on these components should now be unblocked from completing their migrations and can move from using ui/agg_types to plugins.data.search.aggs.

That said, there are a handful of follow up tasks captured in the aggregations roadmap, some of which will include updates to the __LEGACY interfaces which are currently exposed from the aggs service. We will coordinate with affected downstream apps to help make updates as these changes are implemented.