Amazon announced About creating a project OpenSearch , in which the fork of the search platform, analysis and storage platform elasticsearch , as well as the Web platform associated with the platform -Interface Kibana . The code is distributed under the APACHE 2.0 license. In the future it is planned to rename the Amazon Elasticsearch Service service in Amazon OpenSearch Service.
OpenSearch branched from the code base ElasticSearch 7.10.2 . Officially, work on the Formist began on January 21, after which the branch code was cleaned from the components distributed not under the Apache 2.0 license, and replacing the elements of the ElasticSearch brand on OpenSearch. In the current form, the code is still at the alpha testing stage, and in a few weeks the first beta release is expected. Stabilize the code base and make
OpenSearch ready for use in working systems is scheduled for the middle of 2021.
OpenSearch will develop as a joint project developed by community. It is noted that Amazon is currently a curator of the project, but in the future, together with the community, the optimal management strategy will be developed, making decisions and interacting participants involved in development.
The work on OpenSearch has already joined companies like Red Hat, SAP, Capital One and Logz.io. It is noteworthy that Logz.io previously tried to develop his own Fork ElasticSearch, but joined the work on a common project. To participate in the development of OpenSearch, it is not necessary to sign the Property Transfer Agreement (CLA, Contributor License Agreement), and Rules use of the brand OpenSearch are permitted and allow you to specify this name when promoting your products.
The reason for creating Forka was the translation of the ElasticSearch source project for an unscrew license SSPL (Server Side Public License) and termination of the publication of changes under the old APACHE 2.0 license. License SSPL is recognized OSI Organization (Open Source Initiative) Nutritional Open Source Criteria due to the presence of discriminatory requirements. In particular, despite the fact that the SSPL license is based on AGPLV3, there are additional supply requirements under the SSPL license not only the application code itself, but also the source texts of all components involved in the provision of cloud service.