Avoiding failure when using frozen indices #1842
Merged
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.
This commit changes es-hadoop to treat frozen indices as empty indices rather than throwing exceptions. Before
this change if you query a frozen index with es-hadoop or spark you get job failure with an exception like this:
We don't want to change behavior to read frozen indices by default since they will be very slow. We might add some config to have es-hadoop pass in
ignore-throttled
so that frozen indices can be queried. But since they are deprecated that might not be worth the effort.Relates #1734