-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Replace Nest package with Elastic.Clients.Elasticsearch #17021
Comments
We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues). This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here. |
You will need to create a new ElasticSearch module if we want to keep supporting the older versions of ElasticSearch. If you use the new libraries it may break current sites that are using older versions of ElasticSearch. I believe Elastic.Client.Elasticsearch was released with ES 8.0 to mark the change from the open source project it was and the now non-open source project it became. Also, more on this. The new libraries don't support OpenSearch anymore from what I can remember. |
Here for OpenSearch : https://github.com/opensearch-project/opensearch-net |
@Skrypt there is no plan to support both Nest and the new library. The plan is to introduce this as a breaking change and roll out OC 3.0. Where in OC that we use OpenSearch? I am starting a new branch to replace Nest with Elastic.Clients.Elasticsearch. If anyone want to work on this, please ping me first. |
Related to #15977 |
Look at the Elasticsearch PR where I am explaining that OpenSearch works if you are using the version that was out at that time because it was the same. Of course new versions of OpenSearch won't work just as ES 8. There is a compatibility mode but that's surely not as optimized. Now, I don't really care about ES 7 but OpenSearch will eventually need a proper module if we drop the current module. Make sense? |
@Skrypt I don't know much about previous versions of ES. But compatibility mode was to ensure that ES8 works on NEST. Now that we are moving to ES8, why do we need compatibility mode? I completed the migration from NEST to |
Yes, nevermind ... OpenSearch support will be dropped in next release as I understand you guys decided. |
I guess that OpenSearch will need its on module now. If someone has ever time to work on it. |
Compatibility mode was not great that's what I meant. |
Nest package is deprecated are was replaced with Elastic.Clients.Elasticsearch few years back.
Once that is done, we can change the way we deserialize the custom analyzers and custom token-filters. The code will look more like this
The text was updated successfully, but these errors were encountered: