It's currently work in progress but you can already see in tests some of the features like chainable API, composing queries and filters and aggregations:
https://github.com/elasticsearch/elasticsearch-dsl-py/blob/m...
I try to work closely with the fine people at Mozilla currently maintaining ElasticUtils to make sure there is a nice migration path and I don't miss anything obvious. Any feedback would be more than welcome (github, twitter, email, irc #elasticsearch-py, carrier pigeon, ...)!
http://github.com/bitemyapp/bloodhound/
(Intended to act as a guide as well as a practical ES client)
You can lose massive amounts of time debugging a broken query in ES, due in no small part to a lack of an explicit spec.
To respond to the mis-aimed comment:
It's not about just beginning learning - it's a problem the moment you want to properly compose queries and not just have dumb templates.
I am not new to ES, I've been using it for years.
I understand wanting directness and the full breadth of the Elasticsearch API (thus moving away from Haystack), but not actually supporting anything in the API (which is the actual hard work, not wrapping an http-client) is problematic.
I'm excited Andrew decided to work on this during our last hackathon and that now we're able to share it with the community.
We've been really happy with Elasticsearch. Hopefully this library will help more people leverage Elasticsearch in their python projects.
Anyone know of good Ruby alternatives?
thanks!