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

Expand wildcards in snapshot #9903

Merged

Conversation

imotov
Copy link
Contributor

@imotov imotov commented Feb 26, 2015

This PR makes handling of expand_wildcards parameters consistent. The first commit f5d8ca8 will go to both 1.x and master and the second commit 7abe1ed will go into master only. Closes #6097.

@javanna
Copy link
Member

javanna commented Mar 25, 2015

looks good, left a few comments. I think we need to drop the indices options parsing code from multi_search too and reuse this new common method there too.

@javanna
Copy link
Member

javanna commented Mar 25, 2015

One more thing, I would split this PR in two, the actual change and the breaking part that removes the old parameters, otherwise this whole change ends up in the 1.x release notes as a breaking one, which it isn't.

@javanna javanna removed the review label Mar 25, 2015
@imotov imotov force-pushed the issue-6097-expand-wildcards-in-snapshot branch from 7abe1ed to 802b826 Compare March 31, 2015 23:38
@imotov
Copy link
Contributor Author

imotov commented Mar 31, 2015

@javanna I pushed the changes based on your comments. I will open a separate PR for removal of old parameters from 2.0 once this PR is merged.

* If the node represents an array the corresponding array of strings is returned.
* Otherwise the node is treated as a comma-separated string.
*/
public static String[] nodeStringArrayValue(Object node) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I find the node wording confusing, it makes me think of elasticsearch nodes. Maybe xContentNode?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a convention of all static methods that are used to parse XContentMapValues.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok sorry I am not too familiar with these methods :)

@javanna
Copy link
Member

javanna commented Apr 2, 2015

Looks good @imotov , I think we can remove the breaking label?

It might be good to add some more tests where missing around the apis that this PR touches using the different indices options, just to make sure that we still parse them correctly? I have the feeling that we have no extensive tests around that. What do you think?

@imotov imotov removed the >breaking label Apr 14, 2015
@imotov
Copy link
Contributor Author

imotov commented Apr 22, 2015

@javanna I pushed additional tests as we discussed. Could you take a look?

@javanna
Copy link
Member

javanna commented Apr 22, 2015

thanks for adding those tests @imotov LGTM

@imotov imotov force-pushed the issue-6097-expand-wildcards-in-snapshot branch from a011c31 to 7bd4654 Compare April 23, 2015 00:58
@imotov imotov merged commit 7bd4654 into elastic:master Apr 23, 2015
@clintongormley clintongormley changed the title Issue 6097 expand wildcards in snapshot Expand wildcards in snapshot May 29, 2015
@imotov imotov deleted the issue-6097-expand-wildcards-in-snapshot branch May 1, 2020 22:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs >enhancement v1.6.0 v2.0.0-beta1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

snapshot/restore expand_wildcards option not consistent with other apis
4 participants