Add Search APIs for Search Relevance

[ajleong623]

Description

This change adds the recently-created search apis for the search relevance repository. These include:

• /_plugins/_search-relevance/search_configurations/_search
• /_plugins/_search-relevance/experiments/_search
• /_plugins/_search-relevance/query_sets/_search
• /_plugins/_search-relevance/judgments/_search

These give more flexibility in searching through the objects needed for search relevance. The issue and linked PRs are here: opensearch-project/search-relevance#351

Issues Resolved

N/A

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]

Proto Compatibility Report

Merge Report

No changes detected.

---

Generated by Proto Compatibility Check

[github-actions]

Changes Analysis

Commit SHA: 46083bd
Comparing To SHA: fd80768

API Changes

Summary

├─┬Paths
│ ├──[➕] _search (8231:3)
│ ├──[➕] _search (8405:3)
│ ├──[➕] _search (8089:3)
│ └──[➕] _search (8326:3)
└─┬Components
  ├──[➕] requestBodies/search_relevance.query_sets_search (33030:7)
  ├──[➕] requestBodies/search_relevance.experiments_search (32965:7)
  ├──[➕] requestBodies/search_relevance.search_configurations_search (33045:7)
  ├──[➕] requestBodies/search_relevance.judgments_search (32979:7)
  ├──[➕] responses/search_relevance.search_configurations_search___200 (37402:7)
  ├──[➕] responses/search_relevance.judgments_search___200 (37354:7)
  ├──[➕] responses/search_relevance.query_sets_search___200 (37396:7)
  ├──[➕] responses/search_relevance.experiments_search___200 (37280:7)
  └─┬Schemas
    └─┬search_relevance._common___PutSearchConfigurationRequest
      └──[➕] properties/description (69193:9)

Document Element	Total Changes	Breaking Changes
paths	4	0
components	9	0

• Total Changes: 13
• Additions: 13

Report

The full API changes report is available at: https://github.com/opensearch-project/opensearch-api-specification/actions/runs/23570134827/artifacts/6113628079

API Coverage

	Before	After	Δ
Covered (%)	666 (65.23 %)	666 (65.23 %)	0 (0 %)
Uncovered (%)	355 (34.77 %)	355 (34.77 %)	0 (0 %)
Unknown	149	153	4

[ajleong623]

I am not 100% sure if the api specs should be added with the version of OpenSearch that is being pushed or after the version has been pushed. I am also working on passing tests before I switch to "ready for review".

[ajleong623]

When adding the tests, I added the new apis as a new synopsis to test files that were already there. However, the version of OpenSearch where those initial tests were created was 3.1. However, the new apis are added for 3.5. Therefore, I put the version assertion of >=3.5 on those files. Was this the preferred way of handling the testing or is there a better strategy?

[epugh]

Just wanted to share that we are actively using these annotations in the opensearch-mcp-server-py repo to generate tools, very exciting.

Here is an example: opensearch-project/opensearch-mcp-server-py#187

When this goes in, we'll push for another release of the opensearch-py client, which will in turn expose these APIs!

[epugh]

I dropped in a few questions...

[epugh]

funny, yet accurate wording ;-)

[epugh]

Is this correct? tasks? or queries?

[ajleong623]

It should be queries. Thank you.

[epugh]

same question on the descirption as above..

[epugh]

maybe it's a more generic "number of items to return" across all of these?

[epugh]

Hi all, this PR has been sitting for a while, and we want to get it in for 3.6.. I'm pinging recently active maintainers ;-). @harshavamsi @lucy66hw for some help!