Skip to content

Conversation

@dreis2211
Copy link
Contributor

Hi,

this PR fixes #20424 by using org.elasticsearch.Version instead of hardcoding the version.

Cheers,
Christoph

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Mar 9, 2020
@scottfrederick
Copy link
Contributor

At the time we did the upgrade in d282eb6, TestContainers was behind the latest version. This hard-coded version was the minimum required to make the tests work. If everything is back in sync now, it would be better to just remove VersionOverridingElasticsearchContainer altogether and use the default container again.

@dreis2211
Copy link
Contributor Author

@scottfrederick ElasticsearchContainer still uses 6.4.1, so it's not really in sync (maybe I got you wrong though). Nonetheless, it would work with the standard ElasticsearchContainer.

@scottfrederick
Copy link
Contributor

No, I think you're right. If org.elasticsearch.Version is coming from the Elasticsearch client lib that we're getting via dependency management (not from TestContainers as I first thought), then this seems like the safer change.

@snicoll snicoll added type: task A general task and removed status: waiting-for-triage An issue we've not yet triaged labels Mar 9, 2020
@snicoll snicoll added this to the 2.2.6 milestone Mar 9, 2020
@snicoll snicoll self-assigned this Mar 9, 2020
@snicoll snicoll modified the milestones: 2.2.6, 2.3.0.M3 Mar 9, 2020
@snicoll snicoll closed this in 067accb Mar 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: task A general task

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Revisit VersionOverridingElasticsearchContainer

4 participants