Closed lengerad closed 2 years ago
thanks for reporting, I'll test this and fix it shortly hopefuly,
Confirmed. The one thing I did not test yet was indeed broken. I fixed and tested this properly now with our elastic cloud server. So it should work now.
The fix involves adding the ktor auth module and installing using basic authentication. Let me know if you have any further issues with this. I will release a new jar shortly.
Seems to be working! Thanks for a prompt reaction and for fixing 👏
Describe the bug I recently switch from es-kotlin-client but I'm unable to connect to the ES cluster for basic search. I suspect this might be an issue with settings of my ES cluster but since it was working with previous client I'm not sure so posting here first. I found following thread with similar problem here. I guess it might be related to switching to different version of Rest client under the hood? Because all settings (host, port, user) is kept the same from previous usage.
By the observations it seems that it doesn't matter if I put wrong/correct credentials and it still keeps giving the same result - hence it seems it's really not used.
To Reproduce Steps to reproduce the behavior:
I'm using following setup for ES client (as I was used to before):
and ten I just want to search by ids
and result is:
Expected behavior Credentials passed in
KtorRestClient
should be used as it somehow seems that they are missing or invalid.Your context
Kotlin version: 1.7.10 Search client version: search-client:1.99.5 Version of Elasticsearch: "number" : "7.17.1",
Will you be able to help with a pull request?
Optional of course, but do let me know if you plan to do work.