-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
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
Not compatible with elasticsearch>=1.8.0 #65
Comments
Issue created with elasticutils mozilla/elasticutils#292 |
We'd love to try out elastic-git, but compatibility with latest ES is pretty important for our infrastructure. Is upgrading the codebase on your roadmap? |
@infojunkie we'd love see it upgraded but it isn't a huge priority on our roadmap. The biggest issue is that Mozilla's elasticutils isn't being maintained anymore and that's a big dependency for us. The work involved here is either taking over maintenance of elasticutils or swapping it out for an ES library that is maintained while (hopefully) maintaining backwards compatibility to some degree with our existing API. The latter is going to be quite difficult as our API relies heavily on elasticutils' API. |
Yes, I noticed the tight coupling in the code. As far as ES python libs go, I would suggest Elastic's own |
As we get more familiar with |
That'd be awesome! Yes, it's entirely possible. Other than our own team's voluntary contributions, we have no projects currently driving this codebase and so it's not really possible for us to commit to it. |
Is this still an active issue? |
@webmaven yes it is, we haven't upgraded it yet. But we're still using it in production with ES |
How about now? 😀 |
@webmaven we're very happy to accept code contributions but have no capacity to drive this ourselves and will likely not be a priority for us in the future either. |
I want to contribute @webmaven |
The refactor on
elasticsearch 1.8.0
affects the use ofbulk_index
inelasticutils
The text was updated successfully, but these errors were encountered: