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
To allow for a "zero downtime" experience with the new Serverless offering, all internal "Session View" http routes must be versioned. Responses should also have their own types as a means to a path towards backwards compatibility.
see this example PR of work already done by ML team: #156949
It would also be prudent to update all ES queries to limit to fields only Session View needs to display it's data, currently we are pulling the full document.
The text was updated successfully, but these errors were encountered:
…58982)
## Summary
### Issues:
- #158687
- #158686
### Fixes
- API routes now versioned
- Moved index selection logic to session_view plugin, added tests
- fields now defined for all ES queries
- types consolidated, and put under a latest/v1 export paradigm
### Checklist
Delete any items that are not applicable to this PR.
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
To allow for a "zero downtime" experience with the new Serverless offering, all internal "Session View" http routes must be versioned. Responses should also have their own types as a means to a path towards backwards compatibility.
see this example PR of work already done by ML team:
#156949
There is a new Core "versioned" router, so we should update to using that.
see: https://docs.google.com/document/d/1gquGhkn_OMqMCKo6a_2h0ArxzUsbVKtcOi2YFiGPFZ4/edit#bookmark=id.kahpa31pzm9i
https://docs.elastic.dev/kibana-dev-docs/versioning-http-apis#4-adhere-to-the-http-versioning-specification
It would also be prudent to update all ES queries to limit to fields only Session View needs to display it's data, currently we are pulling the full document.
The text was updated successfully, but these errors were encountered: