Skip to content

Commit f3d0214

Browse files
committed
[DOCS] Adds information about compatibility mode in Connecting
1 parent c0dd251 commit f3d0214

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

docs/connecting.asciidoc

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,7 @@ This page contains the information you need to connect and use the Client with
99
* <<client-auth, Authentication options>>
1010
* <<client-usage, Using the client>>
1111
* <<client-faas, Using the Client in a Function-as-a-Service Environment>>
12+
* <<client-comp, Enabling the Compatibility Mode>>
1213

1314
[discrete]
1415
[[client-auth]]
@@ -219,3 +220,11 @@ Resources used to assess these recommendations:
219220

220221
* https://cloud.google.com/functions/docs/bestpractices/tips#use_global_variables_to_reuse_objects_in_future_invocations[GCP Cloud Functions: Tips & Tricks]
221222
* https://docs.aws.amazon.com/lambda/latest/dg/best-practices.html[Best practices for working with AWS Lambda functions]
223+
224+
[discrete]
225+
[[client-comp]]
226+
=== Enabling the Compatibility Mode
227+
228+
The Elasticsearch server version 8.0 is introducing a new compatibility mode that allows you a smoother upgrade experience from 7 to 8. In a nutshell, you can use the latest 7.x Elasticsearch client with an 8.x Elasticsearch server, giving more room to coordinate the upgrade of your codebase to the next major version.
229+
230+
If you want to leverage this functionality, please make sure that you are using the latest 7.x client and set the environment variable `ELASTIC_CLIENT_APIVERSIONING` to `true`. The client is handling the rest internally. For every 8.0 and beyond client, you're all set! The compatibility mode is enabled by default.

0 commit comments

Comments
 (0)