base on Apache Amoro (incubating) is a Lakehouse management system built on open data lake formats. <!-- - Licensed to the Apache Software Foundation (ASF) under one - or more contributor license agreements. See the NOTICE file - distributed with this work for additional information - regarding copyright ownership. The ASF licenses this file - to you under the Apache License, Version 2.0 (the - "License"); you may not use this file except in compliance - with the License. You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. --> <p align="center"> <img src="https://amoro.apache.org/img/amoro-logo.svg" alt="Amoro logo" height="120px"/> </p> <p align="center"> <a href="https://www.apache.org/licenses/LICENSE-2.0.html"> <img src="https://img.shields.io/badge/license-Apache%202-4EB1BA.svg" /> </a> <a href="https://github.com/apache/amoro/actions/workflows/core-hadoop3-ci.yml"> <img src="https://github.com/apache/amoro/actions/workflows/core-hadoop3-ci.yml/badge.svg" /> </a> <a href="https://github.com/apache/amoro/actions/workflows/core-hadoop2-ci.yml"> <img src="https://github.com/apache/amoro/actions/workflows/core-hadoop2-ci.yml/badge.svg" /> </a> <a href="https://github.com/apache/amoro/actions/workflows/trino-ci.yml"> <img src="https://github.com/apache/amoro/actions/workflows/trino-ci.yml/badge.svg" /> </a> </p> Apache Amoro (incubating) is a Lakehouse management system built on open data lake formats. Working with compute engines including Flink, Spark, and Trino, Amoro brings pluggable and self-managed features for Lakehouse to provide out-of-the-box data warehouse experience, and helps data platforms or products easily build infra-decoupled, stream-and-batch-fused and lake-native architecture. Learn more about Amoro at https://amoro.apache.org/, contact the developers and community on the [mailing list](https://amoro.apache.org/join-community/#mailing-lists) if you need any help. ## Architecture Here is the architecture diagram of Amoro: <p align="center"> <img src="https://amoro.apache.org/img/home-content.png" alt="Amoro architecture" height="360px"/> </p> * AMS: Amoro Management Service provides Lakehouse management features, like self-optimizing, data expiration, etc. It also provides a unified catalog service for all compute engines, which can also be combined with existing metadata services. * Plugins: Amoro provides a wide selection of external plugins to meet different scenarios. * Optimizers: The self-optimizing execution engine plugin asynchronously performs merging, sorting, deduplication, layout optimization, and other operations on all type table format tables. * Terminal: SQL command-line tools, provide various implementations like local Spark and Kyuubi. * LogStore: Provide millisecond to second level SLAs for real-time data processing based on message queues like Kafka and Pulsar. ## Supported table formats Amoro can manage tables of different table formats, similar to how MySQL/ClickHouse can choose different storage engines. Amoro meets diverse user needs by using different table formats. Currently, Amoro supports four table formats: * Iceberg format: Users can directly entrust their Iceberg tables to Amoro for maintenance, so that users can not only use all the functions of Iceberg tables, but also enjoy the performance and stability improvements brought by Amoro. * Mixed-Iceberg format: Amoro provides a set of more optimized formats for streaming update scenarios on top of the Iceberg format. If users have high performance requirements for streaming updates or have demands for CDC incremental data reading functions, they can choose to use the Mixed-Iceberg format. * Mixed-Hive format: Many users do not want to affect the business originally built on Hive while using data lakes. Therefore, Amoro provides the Mixed-Hive format, which can upgrade Hive tables to Mixed-Hive format only through metadata migration, and the original Hive tables can still be used normally. This ensures business stability and benefits from the advantages of data lake computing. * Paimon format: Amoro supports displaying metadata information in the Paimon format, including Schema, Options, Files, Snapshots, DDLs, and Compaction information. ## Supported engines ### Iceberg format Iceberg format tables use the engine integration method provided by the Iceberg community. For details, please refer to: [Iceberg Docs](https://iceberg.apache.org/docs/latest/). ### Mixed format Amoro support multiple processing engines for Mixed format as below: | Processing Engine | Version | Batch Read | Batch Write | Batch Overwrite | Streaming Read | Streaming Write | Create Table | Alter Table | |-------------------|------------------------|-------------|-------------|-----------------|----------------|-----------------|--------------|-------------| | Flink | 1.15.x, 1.16.x, 1.17.x | &#x2714; | &#x2714; | &#x2716; | &#x2714; | &#x2714; | &#x2714; | &#x2716; | | Spark | 3.1, 3.2, 3.3 | &#x2714; | &#x2714; | &#x2714; | &#x2716; | &#x2716; | &#x2714; | &#x2714; | | Hive | 2.x, 3.x | &#x2714; | &#x2716; | &#x2714; | &#x2716; | &#x2716; | &#x2716; | &#x2714; | | Trino | 406 | &#x2714; | &#x2716; | &#x2714; | &#x2716; | &#x2716; | &#x2716; | &#x2714; | ## Features - Self-optimizing - Continuously optimizing tables, including compacting small files, change files, regularly delete expired files to keep high query performance and reducing storage costs. - Multiple Formats - Support different table formats such as Iceberg, Mixed-Iceberg and Mixed-Hive to meet different scenario requirements and provide them with unified management capabilities. - Catalog Service - Provide a unified catalog service for all compute engines, which can also used with existing metadata store service such as Hive Metastore and AWS Glue. - Rich Plugins - Provide various plugins to integrate with other systems, like continuously optimizing with Flink and data analysis with Spark and Kyuubi. - Management Tools - Provide a variety of management tools, including WEB UI and standard SQL command line, to help you get started faster and integrate with other systems more easily. - Infrastructure Independent - Can be easily deployed and used in private environments, cloud environments, hybrid cloud environments, and multi-cloud environments. ## Modules Amoro contains modules as below: - `amoro-common` contains core abstractions and common implementation for other modules - `amoro-ams` is amoro management service module - `amoro-web` is the dashboard frontend for ams - `amoro-optimizer` provides default optimizer implementation - `amoro-format-iceberg` contains integration of Apache Iceberg format - `amoro-format-hudi` contains integration of Apache Hudi format - `amoro-format-paimon` contains integration of Apache Paimon format - `amoro-format-mixed` provides Mixed format implementation - `amoro-mixed-hive` integrates with Apache Hive and implements Mixed Hive format - `amoro-mixed-flink` provides Flink connectors for Mixed format tables (use amoro-flink-runtime for a shaded version) - `amoro-mixed-spark` provides Spark connectors for Mixed format tables (use amoro-spark-runtime for a shaded version) - `amoro-mixed-trino` provides Trino connectors for Mixed format tables ## Building Amoro is built using Maven with JDK 8 and JDK 17(only for `amoro-format-mixed/amoro-mixed-trino` module). * Build all modules without `amoro-mixed-trino`: `mvn clean package` * Build and skip tests: `mvn clean package -DskipTests` * Build and skip dashboard: `mvn clean package -Pskip-dashboard-build` * Build and disable disk storage, RocksDB will NOT be introduced to avoid memory overflow: `mvn clean package -DskipTests -Pno-extented-disk-storage` * Build and enable aliyun-oss-sdk: `mvn clean package -DskipTests -Paliyun-oss-sdk` * Build with hadoop 2.x(the default is 3.x) dependencies: `mvn clean package -DskipTests -Phadoop2` * Specify Flink version for Flink optimizer(the default is 1.20.0): `mvn clean package -DskipTests -Dflink-optimizer.flink-version=1.20.0` * If the version of Flink is below 1.15.0, you also need to add the `-Pflink-optimizer-pre-1.15` parameter: `mvn clean package -DskipTests -Pflink-optimizer-pre-1.15 -Dflink-optimizer.flink-version=1.14.6` * Specify Spark version for Spark optimizer(the default is 3.3.3): `mvn clean package -DskipTests -Dspark-optimizer.spark-version=3.3.3` * Build `amoro-mixed-trino` module under JDK 17: `mvn clean package -DskipTests -Pformat-mixed-format-trino,build-mixed-format-trino -pl 'amoro-format-mixed/amoro-mixed-trino' -am`. * Build all modules: `mvn clean package -DskipTests -Ptoolchain,build-mixed-format-trino`, besides you need config `toolchains.xml` in `${user.home}/.m2/` dir with content below. * Build a distribution package with all formats integrated: `mvn clean package -Psupport-all-formats` * Build a distribution package with Apache Paimon format: `mvn clean package -Psupport-paimon-format` * Build a distribution package with Apache Hudi format: `mvn clean package -Psupport-hudi-format` ``` <?xml version="1.0" encoding="UTF-8"?> <toolchains> <toolchain> <type>jdk</type> <provides> <version>17</version> <vendor>sun</vendor> </provides> <configuration> <jdkHome>${YourJDK17Home}</jdkHome> </configuration> </toolchain> </toolchains> ``` ## Quickstart Visit [https://amoro.apache.org/quick-demo/](https://amoro.apache.org/quick-demo/) to quickly explore what amoro can do. ## Join Community If you are interested in Lakehouse, Data Lake Format, welcome to join our community, we welcome any organizations, teams and individuals to grow together, and sincerely hope to help users better use Data Lake Format through open source. Join the Amoro WeChat Group: Add " `kllnn999` " as a friend on WeChat and specify "Amoro lover". ## Contributors This project exists thanks to all the people who contribute. <a href="https://github.com/apache/amoro/graphs/contributors"> <img src="https://contrib.rocks/image?repo=apache/amoro" /> </a> Made with [contrib.rocks](https://contrib.rocks). ## Star History [](https://star-history.com/#apache/amoro&Date) ", Assign "at most 3 tags" to the expected json: {"id":"8965","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"