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
Is your feature request related to a problem? Please describe
Lucene has support for BPReorderingMergePolicy reorganises segments on merge when possible to group related documents together. However it is currently not available within OpenSearch. Such a merge policy can be an alternative to using a strict sort order on an index to improve performance of common filters on an index by encouraging continuous doc IDs for the same field value.
Describe the solution you'd like
Allow for BPReorderingMergePolicy or equivalent to be configure via index settings. This would need to allow for control over:
The fields to partition on
The min and max doc frequency
Control over the minimum doc thresholds for triggering the reordering
Related component
Search:Performance
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
@msfroh yes, thanks for tagging.
I'm in support of exposing this as a setting, maybe something we can add in opensearch 3.0. I will take a look at ways of exposing it post 2.19 release.
Is your feature request related to a problem? Please describe
Lucene has support for
BPReorderingMergePolicy
reorganises segments on merge when possible to group related documents together. However it is currently not available within OpenSearch. Such a merge policy can be an alternative to using a strict sort order on an index to improve performance of common filters on an index by encouraging continuous doc IDs for the same field value.Describe the solution you'd like
Allow for
BPReorderingMergePolicy
or equivalent to be configure via index settings. This would need to allow for control over:Related component
Search:Performance
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: