Expressions Roadmap

[streamich]

This issue tracks all planned or possible work for Expressions service.

Tech debt

General

• Cleanup expression renderer handlers which are only used in Canvas
• Remove uiState from expressions plugin
• Add test coverage

Features

General

• Update forks/namespaces
• Expression inspector panel
• Background search service integration
• New saved object type
  • Convert canvas panel to embeddable
• Expression editor component

Functions

• Enforce serializable input/output on expression function definition
• Create "standard library" of data manipulation functions
• httpGet function to retrieve external datasets

Performance

• Expressions executor caching [WIP] Expressions caching #51160
• Code splitting

Integrations

Documentation

• Audit & update Jsdocs for all public contracts
• Audit & improve help text on any functions we own
• Create Expression explorer plugin
• Update README.md with more detail

Needs discussion

• Making expression interpreter & library of "standard functions" available outside Kibana
• API improvements

[elasticmachine]

Pinging @elastic/kibana-app-arch

[lukasolson]

We also need an issue for reporting progress information (e.g. # of functions executed vs. total), and maybe some mechanism for reporting progress of individual functions.

[streamich]

Breakout:

• Server-side expressions.
  • Discuss various ways to implement them.
  • Support a set of expression functions on server-side as on client side.
    • esaggs
    • other functions
  • Canvas
• Partial search result support (Make-it-slow) in expressions.
  • How do we want to support partial results? Observables or execute expression multiple times or something else?

[streamich]

Notes:

• Caching in make-it-slow. Discussed if we want to do it now and how it will work with make-it-slow.
  • Caching waits on refactoring to be merged first.
• Server-side functions
  • First finish refactoring
  • Implement server-side of expressions
  • Implement esaggs on server
  • Talk with Canvas to migrate to new server-side expressions.
  • Responsibility to register the same function on server and browser falls on implementer on the function.
• Partial results for make-it-slow
  • Decided to postpone for next planning.
  • Reservations about complexity of observable approach.

[vadimkibana]

Closing this as it is too old.

---

@dokmic maybe there is something of interest in this issue for you.