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

Snapshot API : Why is "include_global_state" boolean handled differently from "ignore_unavailable" in the API? #4949

Closed
meconlin opened this issue Jan 30, 2014 · 3 comments

Comments

@meconlin
Copy link

Why is "include_global_state" boolean handled differently from "ignore_unavailable" in the API?

One handles string "true"/"false" one does not?

From CreateSnapshotRequest

} else if (name.equals("ignore_unavailable") ||  name.equals("ignoreUnavailable")) {
                ignoreUnavailable = nodeBooleanValue(entry.getValue());
}

vs.

if (!(entry.getValue() instanceof Boolean)) {
                    throw new ElasticsearchIllegalArgumentException("malformed include_global_state, should be boolean");
}
@imotov
Copy link
Contributor

imotov commented Jan 30, 2014

Because I missed it. I will fix. Thanks for catching it.

@ghost ghost assigned imotov Jan 30, 2014
@meconlin
Copy link
Author

oh fun! can I fix it? love es by the way, thanks for cranking on it. The snapshot api is awesome.

@imotov
Copy link
Contributor

imotov commented Jan 30, 2014

Sure. By the way, RestoreSnapshotRequest has the same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants