Amazon presented the first release of the OpenSearch project, which develops a fork of the Elasticsearch search, analysis and data storage platform and the Kibana web interface. The OpenSearch project also continues to develop the Open Distro for Elasticsearch distribution, which was previously developed at Amazon together with Expedia Group and Netflix in the form of an add-on for Elasticsearch. The code is distributed under the Apache 2.0 license. The OpenSearch 1.0 release is considered ready for use on production systems.
OpenSearch is developing as a collaborative project developed with the participation of the community, for example, companies such as Red Hat, SAP, Capital One and Logz.io have already joined the work. To participate in the development of OpenSearch, you do not need to sign a transfer agreement (CLA, Contributor License Agreement), and the rules for using the OpenSearch trademark are permissive and allow you to indicate this name when promoting your products.
OpenSearch was forked from the Elasticsearch 7.10.2 codebase in January and purged of components not distributed under the Apache 2.0 license. The release includes the OpenSearch storage and search engine, the web interface and data visualization environment OpenSearch Dashboards, as well as a set of add-ons previously supplied in the Open Distro for Elasticsearch product and replacing the paid components of Elasticsearch. For example, Open Distro for Elasticsearch provides add-ons for machine learning, SQL support, notification generation, cluster performance diagnostics, traffic encryption, role-based access control (RBAC), authentication through Active Directory, Kerberos, SAML and OpenID, single sign-on implementation (SSO) and maintaining a detailed log for auditing.
Among the changes, in addition to cleaning up proprietary code, integration with Open Distro for Elasticsearch and replacing Elasticsearch brand elements with OpenSearch, the following are mentioned:
- The package is tailored to ensure a smooth transition from Elasticsearch to OpenSearch. It is noted that OpenSearch provides maximum compatibility at the API level and migrating existing systems to OpenSearch resembles an upgrade to a new release of Elasticsearch.
- Support for ARM64 architecture has been added for the Linux platform.
- Components for embedding OpenSearch and OpenSearch Dashboard into existing products and services are proposed.
- Support for Data Stream has been added to the web interface, allowing you to save a continuously incoming data stream in the form of a time series (slices of parameter values ββtied to time) in different indexes, but with the ability to process them as a single whole (referring to queries by the common name of the resource).
- Provides the ability to configure the default number of primary shards for a new index.
- The Trace Analytics add-on adds support for visualizing and filtering Span attributes.
- In addition to Reporting, support has been added for generating reports according to a schedule and filtering reports by user (tenant).
Let us recall that the reason for creating the fork was the transfer of the original Elasticsearch project to the proprietary SSPL (Server Side Public License) and the cessation of publishing changes under the old Apache 2.0 license. The SSPL license is recognized by the OSI (Open Source Initiative) as not meeting Open Source criteria due to the presence of discriminatory requirements. In particular, despite the fact that the SSPL license is based on AGPLv3, the text contains additional requirements for delivery under the SSPL license not only of the application code itself, but also the source code of all components involved in the provision of the cloud service. When creating the fork, the main goal was to keep Elasticsearch and Kibana in the form of open projects and provide a full-fledged open solution developed with the participation of the community.
Source: opennet.ru