Closed honzakral closed 10 years ago
Added the deprecation info to CHANGELOG and code.
We had a long talk and decided ElasticUtils 0.9 will only support Elasticsearch 0.90 and lower. I'm going to finish up the work and release it ASAP.
Then the next version of ElasticUtils will support Elasticsearch 0.90 and 1.0 and we'll drop support for versions of Elasticsearch prior to 0.90. That'll make some of this code easier and reduce the combination of things we're testing.
What's the roadmap for 1.0 support look like? We're looking to roll out a Django + ES 1.0, and I'd prefer not to reimplement the Django ORM integration =)
setup.py is declares that elasticsearch-py < 1.0 is required, but this PR makes it look like things are mostly compatible. Is that the case?
I just pushed out 0.9 followed by a 0.9.1 today.
Several of us are meeting at PyCon this week and will sprint on ElasticUtils next week and figure out the big plan. Maybe even get some stuff done. If you're going to be at PyCon during the sprint days, feel free to join us!
Groovy. I won't be at PyCon but a bunch of my coworkers will be -- maybe some of them will join you =)
I will definitely be there and will be happy to help with porting and testing.
Any chance of this or something similar being merged soon?
ElasticUtils 0.10 will require Elasticsearch 0.90 or later. Given that, I'm going to close this out and instead remove all the text* support with a big backwards-incompatible note in the CHANGELOG.
With 1.0 elasticsearch has deprecated text queries that elasticutils uses and the official client is split into two branches (and corresponding releases) - fixed the code and added docs on which version to choose.