Remove eland.Client, use Elasticsearch directly #166
Merged
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
stevedodson
approved these changes
Apr 6, 2020
|
@stevedodson I have a plan to use MonkeyType and run the test suite to get a really good starting point then amend the parts that are missing, we'll see how well it works with pandas data types. :) |
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.
Now that Elasticsearch has up-to-date APIs for 7.6+ we shouldn't need a shim with direct access to
perform_request(). If we do go back to having a shim betweenQueryCompilerandelasticsearch-pyit probably won't be a public interface.