Fix wrong reused file bytes in Recovery API reports #11965
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Looks great. Thanks. I'll merge it in. |
bleskes
added
>bug
v2.0.0-beta1
:Distributed/Recovery
clintongormley
added
:Data Management/Stats
mute
pushed a commit
to mute/elasticsearch
that referenced
this pull request
Jul 29, 2015
Simple snapshot.restore test case that also exposes the bug mentioned in elastic#11876 Fix elastic#11876 Closes elastic#11965
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Calling the correct method, reusedBytes() when creating json output.
This fixes #11876.