8.x support

[leifcr]

Any plans for 8.x support? I see there is PR #1025, which should solve it?

[lexpank]

Any update on this one?

[tsrivishnu]

Also waiting for an update on this.

[picandocodigo]

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.

[emptyflask]

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...

[technige]

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.

[jaredbeck]

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.

[xjunior]

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?

[dani-sc]

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.

[siba2893]

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?

[emptyflask]

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.

[gael-ian]

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.

[xjunior]

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.

[bbenno]

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.