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

Improve error messages for _stats with closed indices #13012

Merged
merged 7 commits into from
Apr 22, 2024

Conversation

srikanthpadakanti
Copy link
Contributor

@srikanthpadakanti srikanthpadakanti commented Apr 2, 2024

Description

The expand_wildcards parameter has the following options according to docs:

  • all: Expand to all open and closed indexes, including hidden indexes.
  • open: Expand to open indexes.
  • closed: Expand to closed indexes.
  • hidden: Include hidden indexes when expanding. Must be combined with open, closed, or both.
  • none: Do not accept wildcard expressions.
    all and closed options are supposed to expand on closed indices.

When either of these options are provided while the cluster contains a closed index, a bad request is returned:

{
"error": {
"root_cause": [
{
"type": "index_closed_exception",
"reason": "closed",
"index": "test-index",
"index_uuid": "DH_Phg7YTpSG-KZfAPoddQ"
}
],
"type": "index_closed_exception",
"reason": "closed",
"index": "test-index",
"index_uuid": "DH_Phg7YTpSG-KZfAPoddQ"
},
"status": 400
}

The fix addresses the above addressed issue and it expands the closed index with all and closed options.

Related Issues

Resolves #11180

Check List

  • New functionality includes testing.
    • All tests pass
  • New functionality has been documented.
    • New functionality has javadoc added
  • Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
  • Commits are signed per the DCO using --signoff
  • Commit changes are listed out in CHANGELOG.md file (See: Changelog)
  • Public documentation issue/PR created

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.

Copy link
Contributor

github-actions bot commented Apr 2, 2024

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

Copy link
Contributor

github-actions bot commented Apr 2, 2024

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

Copy link
Contributor

github-actions bot commented Apr 2, 2024

Compatibility status:

Checks if related components are compatible with change 71f5199

Incompatible components

Skipped components

Compatible components

Compatible components: [https://github.com/opensearch-project/custom-codecs.git, https://github.com/opensearch-project/neural-search.git, https://github.com/opensearch-project/flow-framework.git, https://github.com/opensearch-project/observability.git, https://github.com/opensearch-project/job-scheduler.git, https://github.com/opensearch-project/cross-cluster-replication.git, https://github.com/opensearch-project/security-analytics.git, https://github.com/opensearch-project/opensearch-oci-object-storage.git, https://github.com/opensearch-project/geospatial.git, https://github.com/opensearch-project/notifications.git, https://github.com/opensearch-project/k-nn.git, https://github.com/opensearch-project/asynchronous-search.git, https://github.com/opensearch-project/sql.git, https://github.com/opensearch-project/reporting.git, https://github.com/opensearch-project/performance-analyzer-rca.git, https://github.com/opensearch-project/ml-commons.git, https://github.com/opensearch-project/common-utils.git, https://github.com/opensearch-project/security.git, https://github.com/opensearch-project/index-management.git, https://github.com/opensearch-project/anomaly-detection.git, https://github.com/opensearch-project/alerting.git, https://github.com/opensearch-project/performance-analyzer.git]

@reta
Copy link
Collaborator

reta commented Apr 2, 2024

@srikanthpadakanti thanks for the change, could you please add a test case for it as well? thank you

Copy link
Contributor

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

Copy link
Contributor

❌ Gradle check result for f7a1951: 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: srikanth padakanti <srikanth29.9@gmail.com>
@reta
Copy link
Collaborator

reta commented Apr 18, 2024

@mch2 @srikanthpadakanti looking into recent test failures (REST API specs), the behavior that is described as a bug is actually expected. I think there is nothing to fix from the code perspective (apologies to @srikanthpadakanti) but we need to update the documentation instead: the IndexClosedException is supposed to be returned.

Does it make sense? It seems like tests are stable, good sign.

Copy link
Contributor

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

Copy link
Contributor

✅ Gradle check result for c208a44: SUCCESS

Copy link
Contributor

✅ Gradle check result for c208a44: SUCCESS

Copy link
Contributor

❕ Gradle check result for c208a44: UNSTABLE

  • TEST FAILURES:
      1 org.opensearch.action.admin.cluster.node.tasks.ResourceAwareTasksTests.testTaskResourceTrackingDuringTaskCancellation

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

@reta
Copy link
Collaborator

reta commented Apr 19, 2024

@srikanthpadakanti could you please resolve the conflicts? thank you

Signed-off-by: Srikanth Padakanti <srikanth29.9@gmail.com>
@srikanthpadakanti
Copy link
Contributor Author

@reta Please validate and approve. Thanks.

Copy link
Contributor

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

@reta reta added the backport 2.x Backport to 2.x branch label Apr 19, 2024
Copy link
Contributor

✅ Gradle check result for 6de3241: SUCCESS

@reta
Copy link
Collaborator

reta commented Apr 19, 2024

@mch2 @peternied LGTY folks? thank you!

@reta reta merged commit 98009ed into opensearch-project:main Apr 22, 2024
36 of 42 checks passed
@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.x
# Create a new branch
git switch --create backport/backport-13012-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 98009ed9b83d43377e6b3ffa610db7154ff7d200
# Push it to GitHub
git push --set-upstream origin backport/backport-13012-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-13012-to-2.x.

@reta
Copy link
Collaborator

reta commented Apr 22, 2024

@srikanthpadakanti could you please backport manually to 2.x? thank you

@srikanthpadakanti
Copy link
Contributor Author

srikanthpadakanti commented Apr 22, 2024

@srikanthpadakanti could you please backport manually to 2.x? thank you

@reta Done. Here's the PR : #13338

@hdhalter
Copy link

hdhalter commented May 1, 2024

@srikanthpadakanti - Does anything need to change in the documentation, or does it now work according to the documentation? Thanks.

@reta
Copy link
Collaborator

reta commented May 1, 2024

@srikanthpadakanti - Does anything need to change in the documentation, or does it now work according to the documentation? Thanks.

@hdhalter I thinks the change is very internal - no user visible API changes, thank you.

@srikanthpadakanti
Copy link
Contributor Author

@srikanthpadakanti - Does anything need to change in the documentation, or does it now work according to the documentation? Thanks.

Hello @hdhalter No changes needed in documentation. Now the exception message is thrown with clear instructions what needs to be done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API Issues with external APIs backport 2.x Backport to 2.x branch backport-failed bug Something isn't working Indexing Indexing, Bulk Indexing and anything related to indexing v2.14.0 v3.0.0 Issues and PRs related to version 3.0.0
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

[BUG] Error invoking _stats with expand_wildcards on closed indices
5 participants