Optimize UnsignedLong range queries to convert to MatchNoDocsQuery when lower > upper bounds

[Skyring100]

Description

unsignedLongRangeQuery method now returns MatchNoDocsQuery when lower bound > upper bound

Related Issues

Resolves #14404

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]

❌ Gradle check result for 4548b63: 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 add784a: 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 f23212c: UNSTABLE

• TEST FAILURES:

      1 org.opensearch.action.admin.cluster.node.tasks.ResourceAwareTasksTests.testTaskResourceTrackingDuringTaskCancellation

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[reta]

LGTM, thanks @Skyring100 ! Could you please resolved the conflicts? Thank you!

[Skyring100]

I am not sure how to resolve these conflicts. I could not find the ResourceAwareTasksTests class mentioned in the stacktrace on my local machine. I have locally run ./gradlew precommit and ./gradlew spotlessApply, both of which were successful. Is there something about flaky tests affecting this issue?

[github-actions]

❌ Gradle check result for a187f9e: 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 a187f9e: UNSTABLE

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[reta]

@gaobinlong LGTM?

[gaobinlong]

Looks good to me.

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.x
# Create a new branch
git switch --create backport/backport-14416-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d2c08b320b49920e142ec70fa66621305fd4ccf8
# Push it to GitHub
git push --set-upstream origin backport/backport-14416-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-14416-to-2.x.

[reta]

@Skyring100 could you please send the backport to 2.x branch following the instructions from above? thank you.

[Skyring100]

Made the backport pull request though the command "git cherry-pick -x --mainline 1 d2c08b3" returned "fatal: bad object d2c08b3". Hopefully this doesn't cause an issue but provides some more information if there are errors for the request

[Skyring100]

I'd like to apologize for how many issues there have been, I was unaware of the knowledge needed beyond my programming skills. Thank you all for having patience and helping with the pull request.