Skip to content

Conversation

@bpintea
Copy link
Contributor

@bpintea bpintea commented Apr 23, 2021

This adds an async query mode to SQL.
It (re)uses the same request and response async-specific EQL object
parameters.

Also similar to EQL, the running search task can have its state
monitored and canceled and its results stored and deleted, with
intermediary responses not supported (the entire result is available
once search finished).

The initial query and subsequent pagination/scrolling requests will both
be started in the async mode.

This adds an async query mode to SQL.
It (re)uses the same request and response async-specific EQL object
parameters.

Also similar to EQL, the running search task can have its state
monitored and canceled and its results sored and deleted, with
intermediary responses not supported (the entire result is available
once search finished).

The initial query and subsequent pagination/scrolling requests will both
be started in the asyn mode.
bpintea added 15 commits April 23, 2021 18:40
Use sane/safe async default values.
- integration testing missing still.
Abstract reusable transport plugin code where feasible.

(cherry picked from commit 8d5cef141c3a823f28cae6321e4859125c1c1624)
- wrap line.
Add ability to cancel ongoing SQL query task.
Add the async integration tests.
Remove superfluous expected call.
This provides the task ID into the SqlQueryResponse also when building
this for a cursor-based request (not just query-based one).
This extends the async implementation to support working with the text
formats (txt, csv, tsv).
No format spec'ing now throws an exception, adapt to that.
@bpintea
Copy link
Contributor Author

bpintea commented May 20, 2021

Closing in favour of chunking down into a feature-branch. Superseded by #73267.

@bpintea bpintea closed this May 20, 2021
@bpintea bpintea deleted the feat/sql_async branch July 26, 2021 11:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants