Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]indices.forcemerge API spec is missing 'primary_only' param #201

Closed
saimedhi opened this issue Mar 13, 2024 · 2 comments · Fixed by #203
Closed

[BUG]indices.forcemerge API spec is missing 'primary_only' param #201

saimedhi opened this issue Mar 13, 2024 · 2 comments · Fixed by #203
Labels
bug Something isn't working untriaged

Comments

@saimedhi
Copy link
Contributor

saimedhi commented Mar 13, 2024

What is the bug?
indices.forcemerge API spec is missing primary_only param. Param is recently introduced in PR. "primary_only" is available in OpenSearch 3.0+ versions.

Do you have any additional context?

@saimedhi saimedhi added bug Something isn't working untriaged labels Mar 13, 2024
@saimedhi
Copy link
Contributor Author

@Xtansia, could you please check if this test is working as expected in opensearch-net? It will run for OpenSearch Main.

@saimedhi saimedhi changed the title [BUG]indices.forcemerge API spec is missing primary_only param [BUG]indices.forcemerge API spec is missing 'primary_only' param Mar 13, 2024
@Xtansia
Copy link
Collaborator

Xtansia commented Mar 14, 2024

@Xtansia, could you please check if this test is working as expected in opensearch-net? It will run for OpenSearch Main.

The .NET YAML test runner uses the low-level client which allows setting arbitrary query params rather than using the explicitly specified properties. Rust on the other hand does some heuristics and skips tests that use APIs or params that don't yet exist in the client.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working untriaged
Projects
None yet
2 participants