We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Why is "include_global_state" boolean handled differently from "ignore_unavailable" in the API?
One handles string "true"/"false" one does not?
From CreateSnapshotRequest
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"); }
The text was updated successfully, but these errors were encountered:
Because I missed it. I will fix. Thanks for catching it.
Sorry, something went wrong.
oh fun! can I fix it? love es by the way, thanks for cranking on it. The snapshot api is awesome.
Sure. By the way, RestoreSnapshotRequest has the same issue.
RestoreSnapshotRequest
cd9be43
Improve boolean handling in snapshot/restore request parsing
32202d5
Fixes #4949
69a853f
938a2c5
Fixes elastic#4949
imotov
Successfully merging a pull request may close this issue.
Why is "include_global_state" boolean handled differently from "ignore_unavailable" in the API?
One handles string "true"/"false" one does not?
From
CreateSnapshotRequest
vs.
The text was updated successfully, but these errors were encountered: