Revert to Elasticsearch low-level-client with minimal parsing of server-response #179
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
snakefoot
force-pushed
the
revert_149
branch
2 times, most recently
from
8280cb8 to
af3b77d
Compare
snakefoot
force-pushed
the
revert_149
branch
3 times, most recently
from
0234a99 to
8ac44ae
Compare
snakefoot
force-pushed
the
revert_149
branch
from
8ac44ae to
6ff9694
Compare
|
@markmcdowell Actually think this pull-request is a mistake. And one should instead merge #156 |
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.
Reverts #149 to avoid issues in server-response-parsing.
Added new setting
EnableDebugModethat should improve server-error-respone-details