Members of Arctic Maintainer issued a document announcing that the name of the Arctic project has been officially changed to Amoro [/aˈmoro/] . The official website of the project and GitHub have changed synchronously; the original official website named after Arctic, the document and source address will be redirected to Amoro :
-
Official website: https://amoro.netease.com/
-
Documentation: https://amoro.netease.com/docs/latest/
-
Source code: https://github.com/NetEase/amoro
Arctic is a streaming lake warehouse system open-sourced by NetEase in August last year. It adds more real-time scene capabilities on top of Iceberg and Hive; Lakes are more accessible and practical.
The announcement pointed out that the reason for the renaming of the project was that Arctic conflicted with some well-known software trademarks, which was not conducive to long-term planning. for example:
-
Man Group's open source Python database project called Arctic
-
Arctic Components for Dremio
On the other hand, Arctic is more inspired by the Apache Iceberg project,
However, during this year of open source, we found that a lake warehouse management system that can adapt to more data lake formats is more in line with the needs of community users. In the future, we will still build more lake warehouse integration and lake native practices around Iceberg. At the same time, more data lake formats will be connected under the drive of the community. We hope that this open source project can bring some meaningful changes in this direction. For this reason, we hope to give this project a more general name.
We think that the letter A is related to this project (we will talk about it below), so we entered the following propmt in ChatGPT.
Think of a catchy and easy-to-spread software name starting with the letter A, with no more than 6 characters, and avoiding trademark conflicts with known software.
After many corrections and trademark confirmations, it finally got the name Amoro, and also updated a new logo:
Project positioning
The Amoro project will continue to embrace the open source ecosystem and maintain openness, including:
-
Will not make a data lake format from 0
-
Actively connect with different data lake formats driven by the community
-
Actively connect with various computing engines driven by the community
-
Connect services with pluggable architecture as much as possible, such as Kyuubi, message queue
More details can be found in the official announcement .