2.6 KiB
navigation_title, mapped_pages
| navigation_title | mapped_pages | |
|---|---|---|
| Elasticsearch JavaScript Client |
|
Elasticsearch JavaScript Client release notes [elasticsearch-javascript-client-release-notes]
Review the changes, fixes, and more in each version of Elasticsearch JavaScript Client.
To check for security updates, go to Security announcements for the Elastic stack.
% Release notes include only features, enhancements, and fixes. Add breaking changes, deprecations, and known issues to the applicable release notes sections.
% ## version.next [elasticsearch-javascript-client-next-release-notes]
% Release date: Month day, year
% ### Features and enhancements [elasticsearch-javascript-client-next-features-enhancements]
% ### Fixes [elasticsearch-javascript-client-next-fixes]
9.0.0 [elasticsearch-javascript-client-900-release-notes]
Release date: April 8, 2025
Features and enhancements [elasticsearch-javascript-client-900-features-enhancements]
-
Compatibility with Elasticsearch 9.0: All changes and additions to Elasticsearch APIs for its 9.0 release are reflected in this release.
-
Serverless client merged in: the
@elastic/elasticsearch-serverlessclient is being deprecated, and its functionality has been merged back into this client. This should have zero impact on the way the client works by default, except that a newserverModeoption has been added. When it's explicitly set to"serverless"by a user, a few default settings and behaviors are changed:- turns off sniffing and ignores any sniffing-related options
- ignores all nodes passed in config except the first one, and ignores any node filtering and selecting options
- enables compression and
TLSv1_2_method(same as when configured for Elastic Cloud) - adds an
elastic-api-versionHTTP header to all requests - uses
CloudConnectionPoolby default instead ofWeightedConnectionPool - turns off vendored
content-typeandacceptheaders in favor or standard MIME types
Docstrings for types that differ between stack and serverless have also been updated to indicate when that is the case.
-
Improved Cloud ID parsing: when using a Cloud ID as the
cloudparameter to instantiate the client, that ID was assumed to be in the correct format. New assertions have been added to verify that format and throw aConfigurationErrorif it is invalid. See #2694.
% ### Fixes [elasticsearch-javascript-client-900-fixes]