Hey @ralph , this is indeed the problem, let me try to share some thoughts on the matter:
- temporarily, as a quick-win, fork
spring-data-elasticsearchasspring-data-opensearch,
Spring Data Elasticsearch is pretty large project, forking it is an option but at the same time, it will unavoidably lead to yet another painful migration at some point when Spring Data Elasticsearch would introduce Opensearch support.
- add the OpenSearch support already in
spring-data-elasticsearch4.x
That is possible but if we do that in non-breaking fashion, the API would be cumbersome in a sense that Opensearch integration would reuse some classes from Elasticsearch. Or another way - forget reuse, everything is just copy / pasted from Spring Data Elasticsearch to Spring Data Opensearch (== similar to forking in some sense).
- is there anyone who could help out in the refactoring of
spring-data-elasticsearchso that at least it’ll be all ready in October?
Yes, I personally proposed to help @sothawo on several occasions but no luck so far. He has a vision and executes on it (he is doing a great job here, I have no intention to mess it up in any way). Still open to help here, I think that would be the best option to move forward.
if the slides posted on this page are still accurate then Spring 6 will only come out in October, which is a very long way away: Spring 6 And Spring Boot 3 - Spring Cloud
This is interesting: Spring Boot 3 is JDK-17 and jakarta.* based. I think Opensearch 2.x may need some work here (not 100% sure though, never tried that).