You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@dblock large chunk of them is expectable: we do rely on Spring Data Elasticsearch and as such, many classes / inrteraces / beans contain Elasticsearch in their names, no much we can do about it sadly (but there could be some leftovers indeed).
Can our own code, such as this package, move from org.springframework.data.elasticsearch.core to an 'opensearch' namespace?
The org.springframework.data.elasticsearch.core (under test only) is 1:1 copy of the spring-data-elasticsearch test scaffolding, technically we can move it under our own package, I have mentioned it here #1 (comment)
What is the bug?
We have a ton of Elasticsearch references in code, https://github.com/opensearch-project/spring-data-opensearch/search?q=Elasticsearch. What's the plan to deprecate those in favor of OpenSearch?
What is the expected behavior?
All "elasticsearch" becomes "opensearch".
The text was updated successfully, but these errors were encountered: