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
Further, i got a "strange" index response if i use the newer api call with this nest client 7.17.5, the delivered mappings doesnt contains the mapping field attribute "index=false" vs the older Mapping Function call
` return new CreateIndexDescriptor(indexName).Mappings(md => md.Map<TDocument>(m => m.AutoMap(5)));`
NEST/Elasticsearch.Net version: 7.15.5
Elasticsearch version: 8.9.0
Description of the problem including expected versus actual behavior:
Steps to reproduce:
new CreateIndexDescriptor(indexName).Mappings(md => md.Map<TDocument>(m => m.AutoMap(5)));
Or as the new API suggested:
new CreateIndexDescriptor(indexName).Map<TypeMappingDescriptor<TDocument>>(mp => mp.AutoMap(5));
expected is a IndexState object with a correct mapping.
The same APi usage like
descriptor.InitializeUsing(indexState) .Settings(s => s.Setting(UpdatableIndexSettings.MaxNGramDiff, 3)) .Map<TypeMappingDescriptor<TDocument>>(mp => mp.AutoMap(5));
works correctly.
@flobernd Have you an idea please or is this a bug?
The text was updated successfully, but these errors were encountered: