Harsha Vamsi Kalluri

@msfroh thanks for the inputs. Tagging @rishabhmaurya here as well. @rishabhmaurya had the idea of essentially trying to help match_all queries that use a descending sort on a numeric field....

Current steps on this: - Build a custom lucene jar with https://github.com/apache/lucene/issues/12534 changes - Run a custom benchmark on match all query with a numeric desc sort and compare performance...

Preliminary benchmarking results: **Without optimization** Metric | Value | Unit -- | -- | -- | Min Throughput | 1.5 | ops/s | | Mean Throughput | 1.51 | ops/s...

@rishabhmaurya I ran this workload and this task: Workload: [geonames](https://github.com/opensearch-project/opensearch-benchmark-workloads/tree/main/geonames) Task: [desc_sort_population](https://github.com/opensearch-project/opensearch-benchmark-workloads/blob/main/geonames/test_procedures/default.json#L314C25-L314C45) I used an `r5.2xlarge` cluster for both benchmarks. The non optimized run was a regular cluster I had...

Re-running the benchmark on the optimized cluster: ``` | Min Throughput | desc_sort_population | 1.5 | ops/s | | Mean Throughput | desc_sort_population | 1.5 | ops/s | | Median...

@rishabhmaurya here's the segment stats: ``` { "_shards": { "total": 7, "successful": 6, "failed": 0 }, "indices": { "geonames": { "shards": { "0": [ { "routing": { "state": "STARTED", "primary":...

Posting some more number here, same workload and instance but this time with force merging into 1 large segment to see if it could have any impact as well as...

@Dgame I think this is a fair request, let me see if OpenSearch supports these kinds of sort parameters and i'll update this issue.

@dblock I can take a stab at this. From my understanding, `optionalDependencies` exist in npm but don't work in this use case because we would need to somehow pull in...

https://github.com/opensearch-project/OpenSearch/issues/11974 is the failure. @reta @msfroh take a look at this as well?