opensearch support status

Infos:

  • Used Zammad version: 6.5.0-1748277819.c2310408.bookworm
  • Used Zammad installation type: debian package
  • Operating system: Debian 12 bookworm
  • OpenSearch version: 3.0.0

What is the status of the OpenSearch support in Zammad? Are there any plans to support it officially in future?

Will the current OpenSearch version (3.0) work with Zammad 6.5?

Which OpenSearch version will work best with Zammad? Is it generally bad idea to use OpenSearch?

What problem are you trying to solve? Can you describe a use-case?

Hello,

the thing is that the Zammad team will not give you officially support if you use opensearch instead of the reccomended elasticsearch.

If you search the forum you can find some other users using opensearch:
e.g.

Best,
Skip

My use case: I have installed Zammad 6.5 and want to use Opensearch 3.0 instead of Elasticsearch with it.

I see nothing about Opensearch support in documentation, so my guess is that it is not officially supported. But that may be temporal issue and future versions of Zammad will support it. So my first question is about the future of Opensearch support. If Zammad is not planning to support Opensearch, that will probably mean that I will have to stick to Elasticsearch (which I do not like).

My second question is about compatibility. Any chance that Opensearch 3.0 will work properly with Zammad 6.5? I saw some people mention that older versions of Opensearch are working with older versions of Zammad. But I can not find up-to-date information. What is the status of the Opensearch today?

Huh you’re right. I was sure there was a passus in the documentation…
Anyway. Opensearch and Elasticsearch are very close in terms of functionality and search query support.

While you can use it, you have to ensure that it behaves the same like Elasticsearch.
That’s something we’re not testing for so “you’re on your own” on that regard.

I cannot answer your Opensearch specific questions, especially in their versions. If version 3 is like Elasticsearch 8, I’d say most likely working. You have to find that out yourself though. Also you may need to fool Zammad version string wise like skip already mentioned with the linked thread.

As the original thread Zammad 6: Opensearch instead of Elasticsearch - Zammad 6 refuses - #13 by sebix has been closed by Zammad, I guess this is now the continuation.

We are running our Zammad installation with OpenSearch 2.19.1 currently, so I can confirm this combination works.

I just updated my test environment to OpenSearch 3 (GitHub - sebix/zammad-docker-compose at opensearch and GitHub - sebix/zammad at opensearch), but the workflow ran into some error (pull access denied for zammad-local :thinking: ) that I can’t solve ad-hoc.
We used that same environment initially to verify the compatibility of Zammad with OpenSearch 2, so in principle, that method should work.

Referring to an open question in the old thread:

My question (July 2023) in the OpenSearch forum is unanswered to date: Will the ingest-attachment plugin become a module like in ES? - OpenSearch - OpenSearch

compatibility.override_main_response_version was removed from Opensearch 3.0, so no chance 3.0 can work with Zammad, because it checks the version.

That is why I am asking Zammad developers about their plans. If they do not plan to support Opensearch, then Elasticsearch is the only option to go.

1 Like

Maybe @YetAnotherGerrit can say something about this.

I installed latest ElasticSearch 9 and it is not supported too.

I thought that ES support means supporting latest version (currently 9) too. I can not find if it is written in documentation. Is there a way to know, which version of ES is supported by zammad installed with the debian package?

Please kindly read the documentation. We clearly state what’s supported and what’s not:

In that case you might want to adjust the requirements.
It is not possible to use ElasticSearch OSS anymore.
Since that was what I had installed and the update to 6.5 did not work anymore with that version.
In the index “zammad_production_chat_session” there is a flattend field requirement which does let the reindex fail.
It does not work with the old ElasticSearch 7.x and also the old OpenSearch <3.0.
I did not see this mentioned in the Release-Notes for 6.5 as a breaking change. Maybe I did miss it.
I would prefer it, if OpenSearch would get some love :slight_smile:

@tgoti please, for the love of god, do not highjack threads with your issues. This doesn’t belong here.

Sorry, but I thought that it would belong here. As it is the same reason that Zammad 6.5 for example does not work with Opensearch anymore. (Even when it is not officially supported.)