The elasticsearch/elasticsearch package is required for Elasticsearch support after installation

[lkaopremier]

API Platform version(s) affected: 3.0

Description
After adding the elasticsearch/elasticsearch package, I got this error "The elasticsearch/elasticsearch package is required for Elasticsearch support.", When analyzing the source code of the version of elasticsearch I added I realized that the namespace declared in the elasticsearch client is different from the namespace used by Api Platform.

How to reproduce
Using version 3.0 of the Api platform and adding the latest version of the elasticsearch/elasticsearch package finally enabled elasticsearch in the configs, See the official doc.

Additional Context

[alanpoulain]

It's because there is a BC break in Elasticsearch 8: https://github.com/elastic/elasticsearch-php/releases/tag/v8.0.0.
We need to add a conflict with this version.

[darthf1]

Hi @alanpoulain,

Would you be able to give some pointers, on how to properly support both ES 7 and ES 8? I was planning to migrate to ES 8 in a few weeks so depending on the complexity I could give it a go at that time.

Maybe there are examples somewhere how to support multiple versions of a library which uses different namespaces.

Current usages of the Elasticsearch namespace (in 2.6.8):

[alanpoulain]

You probably need to use a facade to abstract the client used. You have an example here: https://github.com/api-platform/core/blob/2.7/src/Util/Inflector.php

[curry684]

I just upgraded api-platform/core to ^3.0 in my composer.json, and accidentally happened to notice that afterwards I got stuck on 3.0.0 without upgrade possibility to 3.0.2. Further investigation got me to this issue, which is all fine and dandy, except that I'm now on 3.0.0, with Elasticsearch 8 deeply embedded in my project. So I should remain stuck on 2.7 for the time being, not 3.0.0, the last version without this conflict.

I would dearly recommend yanking 3.0.0 to prevent this confusion which could've caused me severe headaches had I not run composer outdated directly after upgrading.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.