Skip to content
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

ElasticsearchDevServicesBuildTimeConfig uses elasticsearch:7.17.0, newer versions are available #29523

Closed
rsvoboda opened this issue Nov 28, 2022 · 3 comments · Fixed by #31997
Labels
area/devservices area/elasticsearch area/housekeeping Issue type for generalized tasks not related to bugs or enhancements
Milestone

Comments

@rsvoboda
Copy link
Member

Describe the bug

ElasticsearchDevServicesBuildTimeConfig uses elasticsearch:7.17.0, newer versions are available

https://github.com/quarkusio/quarkus/blame/main/extensions/elasticsearch-rest-client-common/deployment/src/main/java/io/quarkus/elasticsearch/restclient/common/deployment/ElasticsearchDevServicesBuildTimeConfig.java#L32

https://hub.docker.com/_/elasticsearch - 8.5.1 and 7.17.7 are available

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

@quarkus-bot
Copy link

quarkus-bot bot commented Nov 28, 2022

@rsvoboda rsvoboda added area/housekeeping Issue type for generalized tasks not related to bugs or enhancements and removed kind/bug Something isn't working labels Nov 29, 2022
@yrodiere
Copy link
Member

The high-level Elasticsearch client currently bundled with Quarkus only supports ES 7, and we can't upgrade to a new version of that client because it's no longer open-source.

So, unfortunately, we might need to wait until #22622 is merged, because it introduces the replacement client which should officially support ES 8. That would mean waiting until Quarkus 3 (see PR for reasons).

I'm open to suggestions, but since the present issue is only about changing a default that can be overridden by users anyway, I think it's not worth taking too much risks (like trying to make the old high-level Elasticsearch client work with ES 8).

@rsvoboda
Copy link
Member Author

ok, let's wait for #22622

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/devservices area/elasticsearch area/housekeeping Issue type for generalized tasks not related to bugs or enhancements
Projects
None yet
2 participants