{"id":99710,"date":"2021-04-13T10:23:10","date_gmt":"2021-04-13T08:23:10","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/amazon-predstavil-opensearch-fork-platformy-elasticsearch"},"modified":"2021-04-13T10:23:10","modified_gmt":"2021-04-13T08:23:10","slug":"amazon-predstavil-opensearch-fork-platformy-elasticsearch","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/amazon-predstavil-opensearch-fork-platformy-elasticsearch","title":{"rendered":"Amazon has introduced OpenSearch, a fork of the Elasticsearch platform.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Amazon has announced the creation of the OpenSearch project, which includes a fork of the Elasticsearch data search, analysis, and storage platform, as well as the associated web interface Kibana. The code is distributed under the Apache 2.0 license. In the future, the Amazon Elasticsearch Service will be renamed to Amazon OpenSearch Service. <\/p>\n
OpenSearch is forked from the Elasticsearch 7.10.2 codebase. Official work on the fork began on January 21, after which the forked code was cleaned of components not distributed under the Apache 2.0 license, and elements branded as Elasticsearch were replaced with OpenSearch. The code is currently in an alpha testing phase, with the first beta release expected in a few weeks. Stabilizing the codebase and making OpenSearch ready for use in production systems is planned for mid-2021. <\/p>\n
OpenSearch will evolve as a collaborative project developed with community involvement. It is noted that Amazon currently acts as the project steward, but an optimal management, decision-making, and participant interaction strategy will be developed jointly with the community. <\/p>\n
Companies such as Red Hat, SAP, Capital One, and Logz.io have already joined the work on OpenSearch. Notably, Logz.io previously attempted to develop its own Elasticsearch fork but joined the collaborative project instead. Participation in the OpenSearch development does not require signing a Contributor License Agreement (CLA), and the rules for using the OpenSearch trademark are permissive, allowing the name to be used in the promotion of their products. <\/p>\n
The creation of the fork was prompted by the transition of the original Elasticsearch project to a non-free SSPL (Server Side Public License) license and the cessation of publishing changes under the old Apache 2.0 license. The SSPL license has been deemed by the OSI (Open Source Initiative) as not meeting Open Source criteria due to discriminatory requirements. Specifically, although the SSPL license is based on AGPLv3, the text includes additional requirements for supplying not only the application code itself but also the source code of all components involved in providing the cloud service. <\/p>\n
The motivation behind creating the fork is said to be the intention to maintain Elasticsearch and Kibana as open projects and provide a fully open solution developed with community participation. As part of the OpenSearch project, independent development of the Open Distro for Elasticsearch distribution will continue, which was previously developed in collaboration with Expedia Group and Netflix as an extension of Elasticsearch. It included additional features that replaced paid components of Elasticsearch, such as machine learning tools, SQL support, alert generation, cluster performance diagnostics, authentication via Active Directory, Kerberos, SAML, and OpenID, single sign-on (SSO) implementation, traffic encryption support, role-based access control (RBAC), and detailed audit logging. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"