Describe the bug
After some investigation with working with different versions of elastic search I believe there is a compatibility problem with version 8. When using docker and spinning up a local elastic search container it was clear there were connectivity issues. I think rolled the elastic search image from 8.6.x to 6.8.23 and woohoo it worked.
Based on reading some of the error messages it appears to be related to a new attribute that is needed for the client.
It is related to this
https://stackoverflow.com/questions/42826735/nonodeavailableexception-none-of-the-configured-nodes-are-available
With the current version of ES and the java clients, you have to specify a cluster_name when using the java client.
I tried applying it to the URI such as elasticsearch://:9300?cluster.name= but this failed.
There is definately a compatibility issue. I would debug it myself but lack a local java setup to work on this project. Hopefully this helps
Describe the bug After some investigation with working with different versions of elastic search I believe there is a compatibility problem with version 8. When using docker and spinning up a local elastic search container it was clear there were connectivity issues. I think rolled the elastic search image from 8.6.x to 6.8.23 and woohoo it worked. Based on reading some of the error messages it appears to be related to a new attribute that is needed for the client. It is related to this https://stackoverflow.com/questions/42826735/nonodeavailableexception-none-of-the-configured-nodes-are-available With the current version of ES and the java clients, you have to specify a cluster_name when using the java client. I tried applying it to the URI such as elasticsearch://:9300?cluster.name= but this failed.
There is definately a compatibility issue. I would debug it myself but lack a local java setup to work on this project. Hopefully this helps