-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for cancel_after_time_interval #273
Comments
On NodeJS the following workaround might work: opensearch.search(searchParams, { querystring: { cancel_after_time_interval: '2s' }}); |
Once the specs in opensearch-api-specification are updated, the clients being generated can be updated. For all other clients, this parameter needs to be added manually. |
Moving this to opensearch-api-specification to check whether this was added to the specs. |
We have stabilized the OpenAPI spec, if someone wants to take this on, please do! We also support writing tests now :) |
Implemented in #353. |
Is your feature request related to a problem?
From OS 1.0 onwards, a new request query parameter
cancel_after_time_interval
was introduced both for SearchRequest and MSearchRequest to provide cancellation of backend request upon timer expiry. This was done to avoid the wasted resource usage from the requests which client application is not waiting for anymore.What solution would you like?
The support for this request parameter is already merged in from OS 1.0 however the clients doesn't have support for passing it to the backend. Would be great if this parameter support can be added in all the clients
What alternatives have you considered?
N/A
Do you have any additional context?
Issue: opensearch-project/OpenSearch#817
PR: opensearch-project/OpenSearch@e44e890
The text was updated successfully, but these errors were encountered: