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
Right now all codecs in custom-codecs repository delegates to PerFieldMappingPostingFormatCodec present in core OpenSearch. But core OpenSearch switches to CompositeCodec if index has mappings associated with composite index .
What solution would you like?
For indices where composite index is present, we should delegate to CompositeCodec instead of PerFieldMappingPostingFormatCodec.
I can think of couple of solutions :
Handle it based on mapperService.isCompositeIndexPresent() in custom-codecs repository
We can get the default delegate codec from core OpenSearch probably via CodecService based on MapperService inputs.
The text was updated successfully, but these errors were encountered:
Sorry @bharath-techie , missed it, I think it would make sense to align the custom codecs registration with OpenSearch core and take composite indices into account, thank you
Is your feature request related to a problem?
Right now all codecs in
custom-codecs
repository delegates toPerFieldMappingPostingFormatCodec
present in core OpenSearch. But core OpenSearch switches toCompositeCodec
if index has mappings associated with composite index .What solution would you like?
For indices where composite index is present, we should delegate to
CompositeCodec
instead ofPerFieldMappingPostingFormatCodec
.I can think of couple of solutions :
mapperService.isCompositeIndexPresent()
in custom-codecs repositoryThe text was updated successfully, but these errors were encountered: