v2 - Breaking changes
Overview
OpenSearch has several breaking changes, so you must verify your application compatibility using this link:
Remove mapping type
This is the major breaking change and it is not specific to OpenSearch as it was alreay planned by ElasticSearch before the fork
So you must be sure that your applications are not using anymore the "type" parameters.
Here are some solutions regarding products often use with elastic solutions and how to configure them to work with OpenSearch 2.x
Fluentbit
If the client is Fluentbit, the easiest solution is to set the parameter Suppress_Type_Name to On.
It is also possible to change the output plugin to the opensearch native one which is part of Fluentbit since version 1.9.
The following article may prove useful for getting started with Fluentbit and OpenSearch:
Fluentd
If the client is Fluentd it's more tricky. There is also a suppress_type_name but the plugin is using this parameter only if detect an elastic version>=7.
So we need to add to more parameters:
verify_es_version_at_startup to false to not let the plugin detect the version
default_elasticsearch_version to '7'
Here are for exemple the change to be done on the spec of the output plugin we're using in Kubernetes
There is also an output plugin for OpenSearch.
The OpenSearch Plugin is not yet available in Rancher Logging System
Last updated