You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As new versions are released, the features of OpenSearch and Elasticsearch will continue to diverge (ref1ref2). However, i'm wondering if there will be an official statement in the documentation about Temporal's support for OpenSearch in the future.
Currently, only recent versions Elasticsearch are supported. This information will be helpful when deciding on the datastore to use with Temporal
The text was updated successfully, but these errors were encountered:
There may be no issue using OpenSearch as the visibility store today, but some Temporal consumers need at least some assurance that the integration will continue working in the future, before they decide to start using it.
I would feel comfortable using OpenSearch as my visibility store for production workloads if the Temporal team formally supported it by doing things like:
Regular testing of the integration with the documented compatible version pairs. (Whatever the team does to ensure postrgres, mysql, and elasticseach integrations continue to work)
As new versions are released, the features of OpenSearch and Elasticsearch will continue to diverge (ref1 ref2). However, i'm wondering if there will be an official statement in the documentation about Temporal's support for OpenSearch in the future.
Currently, only recent versions Elasticsearch are supported. This information will be helpful when deciding on the datastore to use with Temporal
The text was updated successfully, but these errors were encountered: