Skip to content

Conversation

@axiak
Copy link

@axiak axiak commented Aug 31, 2025

Description

The TermVectorsRequest object accepts a routing field to be set,
but doesn't serialize this value out. This means that it does not
actually get sent to the server, and is ignored.

This change actually respects it, as well as adds a simple test
to ensure that it gets sent.

Related Issues

Resolves #19194

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.

@axiak axiak requested a review from a team as a code owner August 31, 2025 18:31
@github-actions github-actions bot added bug Something isn't working Clients Clients within the Core repository such as High level Rest client and low level client labels Aug 31, 2025
@axiak axiak force-pushed the 2.17-routing-patch branch 2 times, most recently from 3e17281 to eb5ceb1 Compare August 31, 2025 18:35
@github-actions
Copy link
Contributor

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

The TermVectorsRequest object accepts a routing field to be set,
but doesn't serialize this value out. This means that it does not
actually get sent to the server, and is ignored.

This change actually respects it, as well as adds a simple test
to ensure that it gets sent.

Signed-off-by: Michael Axiak <mike@axiak.net>
Signed-off-by: Andrew Ross <andrross@amazon.com>
@andrross
Copy link
Member

andrross commented Sep 4, 2025

Thanks @axiak! I've rebased this PR and added a changelog entry.

@github-actions
Copy link
Contributor

github-actions bot commented Sep 4, 2025

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

github-actions bot commented Sep 5, 2025

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

Signed-off-by: Michael Axiak <mike@axiak.net>
@github-actions
Copy link
Contributor

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

@codecov
Copy link

codecov bot commented Sep 10, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.89%. Comparing base (579830d) to head (9e1582f).
⚠️ Report is 158 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #19195      +/-   ##
============================================
+ Coverage     72.78%   72.89%   +0.10%     
- Complexity    69651    69689      +38     
============================================
  Files          5658     5658              
  Lines        320114   320115       +1     
  Branches      46350    46351       +1     
============================================
+ Hits         233004   233346     +342     
+ Misses        68248    67818     -430     
- Partials      18862    18951      +89     

☔ 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.

@opensearch-trigger-bot
Copy link
Contributor

This PR is stalled because it has been open for 30 days with no activity.

@opensearch-trigger-bot opensearch-trigger-bot bot added the stalled Issues that have stalled label Oct 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working Clients Clients within the Core repository such as High level Rest client and low level client stalled Issues that have stalled

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] High Level REST client does not respect routing filter in mtermvectors

2 participants