-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Support wildcards for getting repositories and snapshots #15151
Support wildcards for getting repositories and snapshots #15151
Conversation
Wondering if it requires some documentation changes? |
you're right, I'll add some docs. |
@dadoonet I've added documentation. Could you review this PR? |
@@ -94,7 +94,8 @@ public void testRepositoryCreation() throws Exception { | |||
assertThat(repositoriesMetaData.repository("test-repo-2").type(), equalTo("fs")); | |||
|
|||
logger.info("--> check that both repositories can be retrieved by getRepositories query"); | |||
GetRepositoriesResponse repositoriesResponse = client.admin().cluster().prepareGetRepositories().get(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we still test prepareGetRepositories()
without any parameter? Unless we test it somewhere else?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no parameter is tested in other places
Left a very small comment about test. It looks good to me. I'd prefer that @bleskes double checks though. |
LGTM |
5bb9006
to
db5594a
Compare
Support wildcards for getting repositories and snapshots
This was only introduced in 2.2 with elastic#15151 so we must not use wildcards when running with 2.0 nodes.
This commit adds multiple repositories support to get snapshots request. If some repository throws an exception this method does not fail fast instead, it returns results for all repositories. This PR is opened in favour of elastic#41799, because we decided to change the response format in a non-BwC manner. It makes sense to read a discussion of the aforementioned PR. This is the continuation of work done here elastic#15151.
Supports the following:
What is not supported:
Relates to #4758