Skip to content

Conversation

@gaobinlong
Copy link
Contributor

Description

See gradle check log: https://build.ci.opensearch.org/job/gradle-check/66006/console, the test is flaky when there're more than 10 documents in the shard 0, so the 2nd page starts from sort value 10, 11, and then a big value 4294967296, so when checking - gt: { hits.hits.2.sort.0: $prev }, the right value and also the expected value is 11, left is 4294967296, we check the type of the expected value firstly and then convert the left value to the same type which is integer :


, so NumberFormatException is thrown.

The solution is to check the sort values reversely from the last document to the first document and use lt instead, at this point, we convert a small value to a long value, no error happens.

Related Issues

#14408

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.

Signed-off-by: Binlong Gao <gbinlong@amazon.com>
@gaobinlong gaobinlong requested a review from a team as a code owner October 23, 2025 14:37
@github-actions
Copy link
Contributor

❌ Gradle check result for 9430754: 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
Copy link
Contributor

❌ Gradle check result for 0c444a5: 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
Copy link
Contributor

❌ Gradle check result for b12ccca: 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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant