What is missing from full feature parity with NEST? about elasticsearch-net HOT 5 CLOSED

Hi @landlord-matt,

With the recent 8.13.* releases, the 8.* client does now support about 95% of the native Elasticsearch features.

If you never used NEST, you probably won't miss anything.

If you have used NEST before, you might notice that some of the helper functions / convenience features are missing. These are built on top of the native functionality and not ported over to the new client (yet). I will bring back some of the functionality over time, but definitely not anything 🙂 An example would be the auto-mapping feature that allowed you to automatically infer Elasticsearch types from CLR types for index creation etc.

Does that answer your question?

Pointing to the migration guide is still valid, because of the missing convenience features and the fundamentally changed architecture. However, this is only a concern if you migrate from NEST to Elastic.Clients.Elasticsearch.

from elasticsearch-net.

Hi @RomBrz

could you tell me where i could look to know if this 95% at april/24 is improved?

I will release a reference documentation (xmldoc rendered by DocFx) shortly. You could use that to compare the API surface of the latest version with the API surface of a pre 8.13 one. This should give you an idea of what has been added in the 8.13.x release.

If the feature parity with NEST now is 100%,

This is not the case and won't ever be the case. The reasons for this are explained in e.g. the migration guide or the 8.0 release notes.

The 95% coverage is about the REST API surface of Elasticsearch. E.g. in the 8.12 client many aggregations were missing which are now supported in 8.13+. Most NEST high level helper functions are not available in the v8 client and some of them will never get re-implemented by design.

My above comment is still valid:

If you have used NEST before, you might notice that some of the helper functions / convenience features are missing. These are built on top of the native functionality and not ported over to the new client (yet). I will bring back some of the functionality over time, but definitely not anything 🙂 An example would be the auto-mapping feature that allowed you to automatically infer Elasticsearch types from CLR types for index creation etc.

the best approach would be update the Client from 7 to 8 while using the 7 Server. When the code is migrated, than migrate the server from 7 to 8 and just point the code to the 8 Server

This is definitely recommended as NEST (v7) will be end-of-life at the end of this year.

The "compatibility mode" on Elastic Server 8 is still working OK with the latest Elastic.Net 7 Client?

Yes.

another approach would be to migrate the server first and put it on compatibility mode ON, than the systems that use Elastic Server could start to migrate the Client from 7 to 8 to use in native mode instead of compatibility mode.

This is possible as well, but the client-first approach is probably easier.

from elasticsearch-net.

This issue is stale because it has been open 5 days with no activity. Remove stale label or comment or this will be closed in 2 days.

from elasticsearch-net.

This issue was closed because it has been stalled for 2 days with no activity.

from elasticsearch-net.

@flobernd could you tell me where i could look to know if this 95% at april/24 is improved?

I'm doing a study to document the platform clients lifecycle and versions, and the ElasticSearch documentation made me a bit confused about migration from Elastic 7 to 8 (both on servers and client sides) considering that much of the documentation talks about the launch date (2022).

One of the sources is this (https://www.elastic.co/guide/en/elasticsearch/client/net-api/current/migration-guide.html) but seems to be made at 8.0 launch (https://www.elastic.co/guide/en/elasticsearch/client/net-api/8.0/migration-guide.html), since the 8.0 and "current" versions have the exact same text.

Right now, if i have a system using Elastic.Net 7 connecting to ElasticSearch Server 7, what should be the best approach to migrate both client and server to 8?

If the feature parity with NEST now is 100%, i understand that the best approach would be update the Client from 7 to 8 while using the 7 Server. When the code is migrated, than migrate the server from 7 to 8 and just point the code to the 8 Server.

The "compatibility mode" on Elastic Server 8 is still working OK with the latest Elastic.Net 7 Client? (Considering that the latest version is from 10/2022).

If it is 100% parity, another approach would be to migrate the server first and put it on compatibility mode ON, than the systems that use Elastic Server could start to migrate the Client from 7 to 8 to use in native mode instead of compatibility mode.

Thanks!

from elasticsearch-net.