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
Before you upgrade, carefully review the Elasticsearch Java Client breaking changes and take the necessary steps to mitigate any issues.
9
-
10
-
To learn how to upgrade, check out <upradedocs>.
8
+
Breaking changes can impact your Elastic applications, potentially disrupting normal operations. Before you upgrade, carefully review the Elasticsearch Java Client breaking changes and take the necessary steps to mitigate any issues. To learn how to upgrade, check [Upgrade](docs-content://deploy-manage/upgrade.md).
The Java API Client source code is generated from a [formal specification of the Elasticsearch API](https://github.com/elastic/elasticsearch-specification). This API specification is large, and although it is tested against hundreds of Elasticsearch test files, it may have discrepancies with the actual API that result in issues in the Java API Client.
@@ -31,7 +29,6 @@ Major releases (e.g. 7.x → 8.x) can include larger refactorings of the API spe
31
29
All Elasticsearch APIs have stability indicators, which imply potential changes. If an API is `stable` only additional non-breaking changes are added. In case of `experimental` APIs, breaking changes can be introduced any time, which means that these changes, will also be reflected in the Java API Client.
32
30
33
31
% ## Next version [elasticsearch-java-client-versionnext-breaking-changes]
34
-
% **Release date:** Month day, year
35
32
36
33
% ::::{dropdown} Title of breaking change
37
34
% Description of the breaking change.
@@ -41,7 +38,6 @@ All Elasticsearch APIs have stability indicators, which imply potential changes.
Review the deprecated functionality for your Elasticsearch Java Client version. While deprecations have no immediate impact, we strongly encourage you update your implementation after you upgrade.
5
+
Over time, certain Elastic functionality becomes outdated and is replaced or removed. To help with the transition, Elastic deprecates functionality for a period before removal, giving you time to update your applications.
6
6
7
-
To learn how to upgrade, check out <upradedocs>.
7
+
Review the deprecated functionality for Elasticsearch Java Client. While deprecations have no immediate impact, we strongly encourage you update your implementation after you upgrade. To learn how to upgrade, check out [Upgrade](docs-content://deploy-manage/upgrade.md).
8
8
9
9
% ## Next version
10
-
% **Release date:** Month day, year
11
10
12
11
% ::::{dropdown} Deprecation title
13
12
% Description of the deprecation.
@@ -17,7 +16,6 @@ To learn how to upgrade, check out <uprade docs>.
Copy file name to clipboardExpand all lines: docs/release-notes/index.md
-2Lines changed: 0 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,6 @@ To check for security updates, go to [Security announcements for the Elastic sta
11
11
% Release notes include only features, enhancements, and fixes. Add breaking changes, deprecations, and known issues to the applicable release notes sections.
0 commit comments