-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[Lens] Integrate search session id #85517
Copy link
Copy link
Closed
Labels
Feature:LensTeam:VisualizationsTeam label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t//Team label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t//enhancementNew value added to drive a business resultNew value added to drive a business result
Metadata
Metadata
Assignees
Labels
Feature:LensTeam:VisualizationsTeam label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t//Team label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t//enhancementNew value added to drive a business resultNew value added to drive a business result
Type
Fields
Give feedbackNo fields configured for issues without a type.
Related to #84908
To enable client side request caching and the "send to background" feature, an important piece of the puzzle is to manage a "search session id". It's created by
const searchSessionId = searchService.session.start();. This id has to be kept around in the state and be passed to the currently running expression. Every time the user hits refresh, changes the filters or the search, a new session id has to be generated.The state should be handled on frame level if possible and be passed down from there.
The session id doesn't have to be persisted.