This is a meta issue to keep track of the work we want to do for the 6.4.0 release individual tickets with the v6.4.0 tag will be created for most of these.
nGram and edgeNGram - https://github.com/elastic/elasticsearch/pull/30209copy_settings default - https://github.com/elastic/elasticsearch/pull/304045 to 1 - https://github.com/elastic/elasticsearch/pull/30587indexed_chars limit - https://github.com/elastic/elasticsearch/pull/31352There a quite a few new API's that need to be mapped:
An unscientific throughput application to measure our different IConnection implementations on how many messages we can pump. For now we only plan to measure _bulk and _search and we'll use the machine learning data set MachineLearningCluster already pulls down.
Will warrant its own [meta] ticket which will be linked here later.
or 2.2 whichever comes first 冒鸥藴赂.
Tests.Throughput vs the already existing implementations/IHttpConnection over to HttpClientFactory. We currently do much of the same but if we don't have to maintain our own pooling of HttpClient instances that would eleviate some complexity in our codebase.ApiGeneration over.DocGeneration over.Add deprecation warnings / changes for nGram and edgeNGram - elastic/elasticsearch#30209
No action needed we are using the non deprecated formats 馃樃
Default shards changing from 5 to 1 - elastic/elasticsearch#30587
No action needed on our end, integration tests still run successfully where we do not explicitly state the number of shards.
Deprecate accepting malformed requests in stored script API - elastic/elasticsearch#28939
No action need on our end.
In the field capabilities API, deprecate support for providing fields in the request body. - elastic/elasticsearch#30157
Our mapping of this API always uses GET so no action needed
Deprecate indexing and querying a context completion field without context - elastic/elasticsearch#30712
We expose a handy CompletionField that folks can use on their POJO's but the validation for this should live on the server.
Consistent encoder names - elastic/elasticsearch#29492
Ascii docs change only.
The new _ignored field enables you to know which fields got ignored at index time because of the ignore_malformed option - elastic/elasticsearch#29658
This new field gets automatically stored. Doesn't like like an action is needed on our end.
date_index_name processor template resolution. - elastic/elasticsearch#31841
Doesn't look like this requires an action on our end (no additional properties).
Extend allowed characters for grok field names - elastic/elasticsearch#31653
No action needed on our end.
Add region ISO code to GeoIP Ingest plugin - elastic/elasticsearch#31669
No action needed unless we want to include another default implementation for the GeoIP target field class.
Remove RestGetAllMappingsAction - elastic/elasticsearch#31129
This has no consequences on our end afaict.
Added max_expansion param to span_multi - elastic/elasticsearch#30913
No action needed on our part, PR ended up reusing and adhering to using bool max clauses rather than introducing a new option.
Add support for indexed shape routing in geo_shape query- elastic/elasticsearch#30760
Our IFieldLookup already exposes routing 馃樃
Make sure that field collapsing supports field aliases - elastic/elasticsearch#32648
Requires no changes on our end.
Fix _cluster/state to always return cluster_uuid- elastic/elasticsearch#30656
No action needed, fixes a behaviour from a previous PR which we covered earlier as well.
Get Mapping API to honour allow_no_indices and ignore_unavailable - elastic/elasticsearch#31507
We have tests for getting mappings from indices that do not exist that still run OK. Im happy to skip this one.
`
Reject forcemerge requests with a body - elastic/elasticsearch#30792
We are not sending a body and our integrations are happy, skipping.
Closing this in favour of https://github.com/elastic/elasticsearch-net/issues/3457
Moved remaining items that we bumped to that ticket.