-
Notifications
You must be signed in to change notification settings - Fork 193
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
[FEATURE] Add support for GET _search API requests #890
Comments
@monica-cira , can you assign it to m if its open & provide more detail about it |
@krisfreedain , is it disabled by-default? Purposefully disabled for HTTP method due to security method? |
@VachaShah @harshavamsi - can you get back to @BeElectronicSakshi on this one? thank you |
This feels like a server-side feature request and should be moved to OpenSearch core. |
@dblock / @krisfreedain , Can you please confirm the status of this issue & above requested query. Thanks |
@VachaShah @harshavamsi - can you get back to @BeElectronicSakshi on this one? thank you |
@VachaShah / @harshavamsi , Could you please me with the above query? Thanks |
@BeElectronicSakshi If the server supports search with |
Is your feature request related to a problem?
An OpenSearch instance may be behind a Firewall that disallows HTTP methods that perform write operations (POST, DELETE, etc.). In this case, the "GET _search" endpoint can be used in order to perform searches against the cluster. The current functionality of the opensearchpy.client.search method hardcodes the POST method, however the same search behaviour can be achieved with the GET method: https://opensearch.org/docs/latest/api-reference/search/
What solution would you like?
Either a new search method that utilizes the GET method in the _search endpoint, or the ability to pass a parameter to the search method that allows configuring either GET or POST in the API call as the method.
What alternatives have you considered?
In order to interact with OpenSearch instances that have restrictions around HTTP methods, then this client library can't be used.
Do you have any additional context?
The text was updated successfully, but these errors were encountered: