Visit the subquery builder recursively

[vibrantvarun]

Description

This PR contains changes to iterate subquery builder recursively.

Related Issues

17829
1269
1251

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 cc79a23: 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.

[codecov]

Codecov Report

Attention: Patch coverage is 75.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 72.44%. Comparing base (5799fe7) to head (2087542).
Report is 41 commits behind head on main.

Files with missing lines	Patch %	Lines
...nsearch/index/query/ConstantScoreQueryBuilder.java	50.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #17953      +/-   ##
============================================
- Coverage     72.57%   72.44%   -0.14%     
+ Complexity    67066    66969      -97     
============================================
  Files          5470     5473       +3     
  Lines        309697   309816     +119     
  Branches      45045    45062      +17     
============================================
- Hits         224776   224459     -317     
- Misses        66602    67003     +401     
- Partials      18319    18354      +35     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[vibrantvarun]

@msfroh Can you review this PR once as you have the most context on this one. There are few bugs and it resolves all of them.

[github-actions]

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

[vibrantvarun]

Check is failing due to flaky tests. @getsaurabh02 how can we merge this PR?

[prudhvigodithi]

Hey @vibrantvarun,
Here is the summary of all the flaky failures related to this PR. I have re-triggered the Gradle check, but FYI there are some mechanisms in progress #17939 #17974 to deal with the flaky tests. With green Gradle check maintainers should be able to merge the PR.

[github-actions]

❌ Gradle check result for 2087542: 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 2087542: SUCCESS