delegate getMin/getMax methods for ExitableTerms

[HUSTERGS]

Description

ExitableTerms should delegate getMin/getMax methods, or else the getMax() from

OpenSearch/server/src/main/java/org/opensearch/search/sort/FieldSortBuilder.java

Lines 660 to 664 in 4ae7ff3

	Terms terms = MultiTerms.getTerms(reader, fieldType.name());
	if (terms == null) {
	return null;
	}
	return terms.getMin() != null ? new MinAndMax<>(terms.getMin(), terms.getMax()) : null;

will call the default implementation, which is a slow path, and will get a flamegraph like below

Related Issues

Resolves #[Issue number to be closed when this PR is merged]

Check List

• Functionality includes testing.
• API changes companion pull request created, if applicable.
• Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

PR Reviewer Guide 🔍

(Review updated until commit 48e447d)

Here are some key observations to aid the review process:

🧪 No relevant tests

🔒 No security concerns identified

✅ No TODO sections

🔀 No multiple PR themes

⚡ Recommended focus areas for review Formatting Error The CHANGELOG entry has a double dash prefix (- -) instead of a single dash (-), which is a formatting mistake that should be corrected. - - Delegate getMin/getMax methods for ExitableTerms ([#20775](https://github.com/opensearch-project/OpenSearch/pull/20775))

[github-actions]

Persistent review updated to latest commit 2e85d39

[github-actions]

❌ Gradle check result for 2e85d39: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[bugmakerrrrrr]

LGTM

[github-actions]

❌ Gradle check result for 2e85d39: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 2e85d39: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 2e85d39: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 2e85d39: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 48e447d: null

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

Persistent review updated to latest commit 48e447d

[github-actions]

❌ Gradle check result for 48e447d: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

Persistent review updated to latest commit 48e447d

[github-actions]

❌ Gradle check result for 48e447d: null

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

Persistent review updated to latest commit 48e447d

[github-actions]

✅ Gradle check result for 48e447d: SUCCESS