Peter-Josef Meisch

With the implementation of #2083 it is now possible to use a named query like this: ``` @Query(""" { "match": { "text": { "query": "#{#foo}" } } } """) SearchHitssearchByFoo(String...

Will have a look at the injection issue. As for the SpEL stuff: It's hard to know what's available in spring-data-commons without following every PR/change, I didn't find anything about...

This was fixed with #2389, now both the imperative and reactive code now throw a `org.springframework.data.elasticsearch.NoSuchIndexException`.

Started working on that, but it seems that the necessary API calls are missing from the client (https://github.com/elastic/elasticsearch-java/issues/520)

@sabareeshkkanan what do you mean when referring to >Spring Data ES supports rolling index strategy Something along the line of using index templates how I described it in [this post](https://www.sothawo.com/2020/11/implement-a-rolling-index-strategy-with-spring-data-elasticsearch-4-1/)?...

Just saw that this originally is an old issue. Might be worth to add a small example to the code. @mp911de I added this to my list of things to...

same comment as in #593, can add a small example (time question 😄)

Seeing the same when switching to any version higher than 1.8.0: ``` [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 36.059 s [INFO] Finished at: 2023-04-15T09:27:22+02:00 [INFO] ------------------------------------------------------------------------...

Now we have 8.12.0, but it still returns 8.11.0

We are removing the Elasticsearch RestHighLevelClient, but your code is derived from the abstract class that is the base for the old and new client, so this removal should not...