Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[ReactiveElasticsearchTemplate] port defaults to 9200 even when it's not wanted

See original GitHub issue

Hello, Today I was playing with this project. I was testing standard template where everything seems to work and also reactive where I had a problem like described on this SO question. The problem is that we are not using port at all, or at least our url to the elastic doesn’t have the port and it’s working with standard client. When I test the same url in reactive template then I had an error where the port 9200 was appended to the end.

Can somebody please clarify what is the configuration for ReactiveElasticsearchTemplate when the url doesn’t contain port?

Thanks

Issue Analytics

State:
Created 3 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

sothawocommented, Feb 10, 2021

Spring Data Elasticsearch does not use - as well as the other Spring Data modules - configuration entries.

These configuration entries and the whole autoconfiguration stuff is part of Spring Boot. Spring Boot uses these entries to configure Spring Data Elasticsearch, so you would probably need to address this issue with the boot team.

0reactions

bilakcommented, Feb 10, 2021

@sothawo sorry for bothering, but wasn’t there plan to reuse the configuration uris spring.elasticsearch.rest.uris for autoconfiguration of reactive rest template? It shouldn’t be that hard to parse those informations from URL.