What is missing from full feature parity with NEST?

[landlord-matt]

Is your feature request related to a problem? Please describe.
We been using the new Elasticsearch client library Elastic.Clients.Elasticsearch for a while now and everything seems to be working as intended. However, the README of repository here as well as the official Elasticsearch documentation seems to suggest we should still use this with caution. (or at least 8.0.x).

The 8.0.x versions do not offer complete feature parity with the existing NEST client. We therefore recommend you thoroughly review our release notes and migration guidance before attempting to migrate existing applications to the Elastic.Clients.Elasticsearch library.

Describe the solution you'd like
The read me should clarify if this is still accurate and if this is the case, link to some sort of list of missing features.

Perhaps this was an attempt of this (says TBD). If nobody can think of anything, perhaps we should remove the warning against using it?

Describe alternatives you've considered
Simply writing that this is resolved since the added support for completion fields.

Additional context
That's pretty much it

[flobernd]

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.

[github-actions]

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.

[github-actions]

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