Snapshot của apache/hudi: 6.4k★ · Java. Upserts, Deletes And Incremental Processing on Big Data.
Tóm tắt dựng từ metadata GitHub của chính dự án — chưa có bài review TopGit. Trang sẽ tự động cập nhật khi bài review đầy đủ được xuất bản.
VÌ SAO CHƯA CÓ REVIEW
TopGit viết bài đầy đủ cho repo có nhiều sao nhất và được yêu cầu nhiều nhất. Trang này là snapshot trong thời gian chờ — xem README gốc ở tab READ ME.
Apache Hudi is an open data lakehouse platform, built on a high-performance open table format
to ingest, index, store, serve, transform and manage your data across multiple cloud data environments.
https://hudi.apache.org/
Features
Hudi stores all data and metadata on cloud storage in open formats, providing the following features across different aspects.
Ingestion
Built-in ingestion tools for Apache Spark/Apache Flink users.
Supports half-dozen file formats, database change logs and streaming data systems.
Connect sink for Apache Kafka, to bring external data sources.
Storage
Optimized storage format, supporting row & columnar data.
Timeline metadata to track history of changes
Automatically manages file sizes, layout using statistics
Savepoints for data versioning and recovery
Schema tracking and evolution.
Indexing
Scalable indexing subsystem to speed up snapshot queries, maintained automatically by writes.
Tracks file listings, column-level and partition-level statistics to help plan queries efficiently.
Record-level indexing mechanisms built on row-oriented file formats and bloom filters.
Logical partitioning on tables, using expression indexes to decouple from physical partitioning on storage.
Writing
Atomically commit data with rollback/restore support.
Fast upsert/delete support leveraging record-level indexes.
Snapshot isolation between writer & queries.
Optimistic concurrency control to implement relational data model, with Read-Modify-Write style consistent writes.
Non-blocking concurrency control, to implement streaming data model, with support for out-of-order, late data handling.
Queries
Hudi supports different types of queries, on top of a single table.
Snapshot Query - Provides a view of the table, as of the latest committed state, accelerated with indexes as applicable.
Incremental Query - Provides latest value of records inserted/updated, since a given point in time of the table. Can be used to "diff" table states between two points in time.
Change-Data-Capture Query - Provides a change stream with records inserted or updated or deleted since a point in time or between two points in time. Provides both before and after images for each change record.
Time-Travel Query - Provides a view of the table, as of a given point in time.
Read Optimized Query - Provides excellent snapshot query performance via purely columnar storage (e.g. Parquet), when used with a compaction policy to provide a transaction boundary.
Table Management
Automatic, hands-free table services runtime integrated into Spark/Flink writers or operated independently.
Configurable scheduling strategies with built-in failure handling, for all table services.
Cleaning older versions and time-to-live management to expire older data, reclaim storage space.
Clustering and space-filling curve algorithms to optimize data layout with pluggable scheduling strategies.
Asynchronous compaction of row oriented data into columnar formats, for efficient streaming writers.
Consistent index building in face of ongoing queries or writers.
Catalog sync with Apache Hive Metastore, AWS Glue, Google BigQuery, Apache XTable and more.
To build for integration tests that include hudi-integ-test-bundle, use -Dintegration-tests.
To build the Javadoc for all Java and Scala classes (project should be already compiled):
# Javadoc generated under target/site/apidocs
mvn javadoc:aggregate -Pjavadocs
Build with different Spark versions
The default Spark 3.x version, corresponding to spark3 profile is
3.5.3. The default Scala version is 2.12. Scala 2.13 is supported for Spark 3.5 and above.
Refer to the table below for building with different Spark and Scala versions.
Maven build options
Expected Spark bundle jar name
Expected Spark native bundle jar name
Notes
(empty)
hudi-spark3.5-bundle_2.12
hudi-spark3.5-native-bundle_2.12
For Spark 3.5.x and Scala 2.12 (default options)
-Dspark3.3
hudi-spark3.3-bundle_2.12
none
For Spark 3.3.2+ and Scala 2.12
-Dspark3.4
hudi-spark3.4-bundle_2.12
hudi-spark3.4-native-bundle_2.12
For Spark 3.4.x and Scala 2.12
-Dspark3.5 -Dscala-2.12
hudi-spark3.5-bundle_2.12
hudi-spark3.5-native-bundle_2.12
For Spark 3.5.x and Scala 2.12 (same as default)
-Dspark3.5 -Dscala-2.13
hudi-spark3.5-bundle_2.13
hudi-spark3.5-native-bundle_2.13
For Spark 3.5.x and Scala 2.13
-Dspark4.0
hudi-spark4.0-bundle_2.13
hudi-spark4.0-native-bundle_2.13
For Spark 4.0 and Scala 2.13 (Needs java 17)
-Dspark4.1
hudi-spark4.1-bundle_2.13
hudi-spark4.1-native-bundle_2.13
For Spark 4.1 and Scala 2.13 (Needs java 17)
-Dspark4.2
hudi-spark4.2-bundle_2.13
none
For Spark 4.2 and Scala 2.13 (Needs java 17)
-Dspark3
hudi-spark3-bundle_2.12 (legacy bundle name)
none
For Spark 3.5.x and Scala 2.12
hudi-spark-native-bundle is hudi-spark-bundle plus Apache DataFusion Comet
for native vectorized execution, built by the same Maven options. Comet publishes one artifact per
Spark minor version, so the native bundle exists only where that artifact does, and -Dspark3 is a
legacy alias that selects none. It builds on Java 11 but needs Java 17 and Linux with glibc at runtime.
See packaging/hudi-spark-native-bundle/README.md.
Hudi uses ZSTD as the default Parquet compression codec with Spark 3.5 and newer. Spark 3.3 and 3.4
retain GZIP because Hudi's non-vectorized file-group reader uses parquet-java 1.12.x and can leak
off-heap memory when reading ZSTD files (PARQUET-2160).
Upgrade to Spark 3.5 or newer before using ZSTD. Keeping GZIP as the write default does not remove the
risk when an older Spark runtime reads ZSTD files produced by another engine.
Please note that only Spark-related bundles, i.e., hudi-spark-bundle, hudi-utilities-bundle,
hudi-utilities-slim-bundle, can be built using scala-2.13 profile. Hudi Flink bundle cannot be built
using scala-2.13 profile. To build these bundles on Scala 2.13, use the following command:
# Build against Spark 3.5.x and Scala 2.13
mvn clean package -DskipTests -Dspark3.5 -Dscala-2.13 -pl packaging/hudi-spark-bundle,packaging/hudi-utilities-bundle,packaging/hudi-utilities-slim-bundle -am
Starting from versions 0.11, Hudi no longer requires spark-avro to be specified using --packages
Build with different Flink versions
The default Flink version supported is 2.2. The default Flink 2.2.x version, corresponding to the flink2.2 profile, is 2.2.1.
Flink is Scala-free since 1.15.x, there is no need to specify the Scala version for Flink 1.15.x and above versions.
Refer to the table below for building with different Flink and Scala versions.
Maven build options
Expected Flink bundle jar name
Notes
(empty)
hudi-flink2.2-bundle
For Flink 2.2 (default options)
-Dflink2.2
hudi-flink2.2-bundle
For Flink 2.2 (same as default)
-Dflink2.1
hudi-flink2.1-bundle
For Flink 2.1
-Dflink2.0
hudi-flink2.0-bundle
For Flink 2.0
-Dflink1.20
hudi-flink1.20-bundle
For Flink 1.20
-Dflink1.19
hudi-flink1.19-bundle
For Flink 1.19
-Dflink1.18
hudi-flink1.18-bundle
For Flink 1.18
For example,
# Build against Flink 2.2.x
mvn clean package -DskipTests -Dflink2.2
Running Tests
Unit tests can be run with maven profile unit-tests.
mvn -Punit-tests test
Functional tests, which are tagged with @Tag("functional"), can be run with maven profile functional-tests.
mvn -Pfunctional-tests test
Integration tests can be run with maven profile integration-tests.
mvn -Pintegration-tests verify
To run tests with spark event logging enabled, define the Spark event log directory. This allows visualizing test DAG and stages using Spark History Server UI.
mvn -Punit-tests test -DSPARK_EVLOG_DIR=/path/for/spark/event/log
Quickstart
Please visit https://hudi.apache.org/docs/quick-start-guide.html to quickly explore Hudi's capabilities using spark-shell.
Contributing
Please check out our contribution guide to learn more about how to contribute.
For code contributions, please refer to the developer setup.
Có — apache/hudi phát hành theo license Apache-2.0, nghĩa là mã nguồn mở để đọc, fork và (tùy license) tái sử dụng. Mã: github.com/apache/hudi.
apache/hudi có trang demo không?
Dự án có trang chủ ở https://hudi.apache.org/. Tab "Readme" ở trang này thường có ảnh chụp và hướng dẫn bắt đầu nhanh.
apache/hudi còn đang phát triển không?
Commit gần nhất trên apache/hudi là 5 ngày trước (theo timestamp GitHub). Repo có 2.5k fork — một chỉ báo về mức độ quan tâm của cộng đồng.
apache/hudi dùng license gì?
apache/hudi phát hành theo license Apache-2.0. Nên mở file LICENSE trên GitHub để xác nhận — license metadata đôi khi lệch với thực tế dự án.
Đọc thêm về apache/hudi ở đâu?
Trang TopGit này là một snapshot — tab "Readme" hiển thị nguyên văn README của repo (đã bỏ link, giữ ảnh). Repo GitHub ở github.com/apache/hudi là nguồn chính thức.
Đọc đầy đủ README ở tab phía trên.
Vẫn đang phân vân về hudi?
Một cú bấm sẽ gửi câu hỏi kèm trang này cho AI — xem AI nói gì về hudi.