-
Notifications
You must be signed in to change notification settings - Fork 185
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
[BUG] #790
Comments
I believe the You can use A good place to ask questions may be the #clients channel on the public slack. There are many working samples in https://github.com/opensearch-project/opensearch-py/tree/main/samples to try out first, too. |
Hi. Thank you for your prompt answer. I have removed "https://" from host name (thank you for link to github samples, I should have had a look at this page earlier). The corrected code is however not working. Below is the log. On the client side I am using the latest version of Linux Mint (22 Wilma) - maybe it is the problem? The installation instructions at https://opensearch.org/docs/latest/getting-started/quickstart/ do not work for this linux release too (docker-compose exits with errors at 'sudo docker-compose up -d' command with opensearch example yaml file). And here is the error log for the corrected python source: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
The "Remote end closed connection without response" error means the server didn't respond with anything the client expected. Since it looks like you can do I do notice |
Thank you very much, setting use_ssl to True solves the problem. |
What is the bug?
I am sending requests to opensearch engine like:
which correctly returns an answer. I can also use correctly the following python code to send requests and receive answers:
But when I use opensearch python client:
I get the following error:
The above exception was the direct cause of the following exception:
During handling of the above exception, another exception occurred:
Any help is appreciated
The text was updated successfully, but these errors were encountered: