Elasticsearch-rails VS (re) Gem bus (Elasticsearch and Rails 3.2)

Question

I want to integrate Elasticsearch with my Rails 3.2 application. I used to use Tire and it was perfect and direct, now it has retired based on its documentation

NOTIFICATION. This library was renamed and removed in September 2013 (read the explanation). It is not considered compatible with Elasticsearch 1.x.

and this applies to the new set of elasticsearch gemstones , but is it mature enough? have a community? textbooks and how to do? which led me to this question and the karmi answers myself! Now I'm confused which stone to use?

We need a stone that is fully supported and provides a full implementation of elasticsearch functions; since my project is a long-term one and we will use the search engine intensively.

Any help is appreciated!

Answer 1

The Elasticsearch Gem Set is designed and maintained by Elasticsearch as an official Ruby / Rails client. Please note that karmi is the developer of a new package for Ruby. Please read the blog post - release customers! ruby, python, php, perl for more details.

Some highlights

Tire managed to solve many problems for a good integration of Ruby and Rails, and also managed to make some serious bad decisions. Today marks a new start for me, and for users of Ruby Elasticsearch. Today a set of clients with a common design and semantics has been released, the purpose of which is to create a solid foundation for further expansion, integration and experimentation.

...

If you liked Tire, you can be sure that all the amenities for painless Rails integration will be available soon. If you hated Tire, Id would like to invite you to hit the tires on the new Ruby client. I took great care to avoid all of Tire’s bad decisions and make the library - or essentially a collection of three libraries - as modular, expandable, and reliable as I could. Your feedback, opinions and criticism - either through Github questions, through IRC, or by email - are welcome!

...

Since we wrote these clients and they are tested by us, we can provide them with official support. When errors are found, we can quickly fix them - this is our job.

Hope this helps.