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
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:
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: