elasticsearch-rails
elasticsearch-rails copied to clipboard
elastic
8.x support
We'll eventually update the gem and publish a new release for 8.x, but we can't commit to a date at the moment.
So then is there currently any way to use elasticsearch-rails on an app that also has faraday '~> 2.0'? It looks like only elasticsearch-transport '>= 8.1' supports a modern Faraday version, but it's incompatible with the latest elasticsearch-rails.
Frustrating, since ES 8.0 has been out for > 8 months, and this is commercial software...
Hi @emptyflask. I'm sorry that we're not able to provide a timescale for an 8.x release at this time, and I do appreciate how frustrating this must be for you. Unlike the clients, which are our primary focus, we're only able to keep this project updated on a best-effort basis right now.
If you wish to discuss this in more detail for your specific case, please contact your support channel.
This is the last blocker in my app preventing our upgrade to Faraday 2.
elasticsearch-persistence -> elasticsearch 7 -> elasticsearch-transport 7 -> faraday 1
Looking forward to a release, thanks for your work.
It looks like the latest elasticsearch-model 7.x library (7.12.1 right now), along with the rest of the 7 suite (elasticsearch-rails, elasticsearch-ruby) work well with elasticsearch 8 (on my limited test scope). Are there concerns for this setup?
Hi @technige ,
even if there is no date when we can expect 8.x support - is it planned after all, or is it advised to stop relying on this gem altogether? It is currently blocking our update to 8.*, as we rely heavily on it.
Hey I'm also having issues with faraday as the WhatsApp ruby ask ten uses faraday 2.3 and this one is stuck with faraday 1.7. How can we resolve this issue?
It's not ideal if you already have things built around this gem, but searchkick doesn't have this issue, and provides some nice features out of the box like reindexing without downtime. I've migrated some of our projects from elasticsearch-rails to searchkick and it's worked well so far.
Is there a list of what have to be done before any elasticsearch 8.x compatible release? If we know what's expected, maybe some of us can help.
I seriously do not understand how we're getting to version 8.6 of ES and all other languages except Ruby already support it. This issue specifically is 10m/o and we don't even get an answer about what's going on or how we can help.
Probably off-topic, but also due to this issue being still open, I decided to turn my back on ES and migrated to Meilisearch, whose Rails gem also offers a nicer interface, IMHO.
FYI, the elasticsearch-ruby gem IS compatible with 8.6, but the elasticsearch-rails gem is not.
https://github.com/elastic/elasticsearch-ruby
That said, I agree, a ten-month delay in getting elasticsearch-rails up to snuff is not acceptable. Either Elastic should light this candle or decide to stop supporting Rails. Which would be a terrible mistake.
@jeffkirk1 yep, you're right. Also, this gem DOES work with an ES 8.6 backend, but it's awkward to do so. Also, by using elasticsearch-rails v7, we cannot update elasticsearch-ruby to 8.
Please, Elastic, let's get this done. All the people above are also willing to help if we're told what it takes.
We have the same issue here, the missing v8 support is blocking us from upgrading.
A branch supporting v8 has been created. https://github.com/elastic/elasticsearch-rails/commits/8.x
A branch supporting v8 has been created. https://github.com/elastic/elasticsearch-rails/commits/8.x
Is this branch already usable, or is it still in alpha / beta?
The 8.x branch is work in progress. There are still some failing tests in elasticsearch-model that need to be fixed and some further testing and updates before I can publish an official release. But feel free to test it and report any issues. Just be aware that this is code in development and not an official release yet.
My team can't wait any longer for this issue, and will no longer be able to use this gem. Fortunately, our app only uses Elasticsearch::Persistence::Repository, and we were able to write a limited replacement (search, save, and delete only) using only the lower-level elasticsearch gem. If it would help someone else, I'd be happy to share a redacted gist of some of that work.
I appreciate this is frustrating, but I can't provide a timeframe just now. This is still a project on a best-effort basis. It would really help if folks interested tested the 8.x branch and reported any issues or opened Pull Requests for fixes to that branch to get it closer to a release.
Elasticsearch Rails 8.0.0.pre is now available. Please let us know of any issues. Thanks to everyone who's contributed to 8.x.