Unverified50% confidenceFactExact time
Iceberg table metadata uses a multi-level tree structure: table snapshot -> manifest list -> manifest file -> data file, and the query engine must fully read the entire metadata tree during the planning phase.
1
Sources
50%
Confidence
Long-term
Relevance
10/14/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedIceberg is an open table format for data lakes, and its metadata hierarchy is: table metadata JSON → manifest list → manifest file → data file, where each manifest file records data file paths, partitions, column-level statistics and file-level statistics.74% similarUnverifiedIceberg's manifest files are Avro files, and each entry contains the file path, the partition it belongs to, record count, file size, and statistics such as the upper and lower bounds and null counts for each column; query planning uses these statistics and partition information to prune data files.70% similarUnverifiedFigma将每个设计文件组织为一棵Scene Graph（场景图）树状数据结构66% similarUnverifiedApache Iceberg's table metadata layer is separated from data files, allowing catalogs to attach governance attributes without modifying the underlying data.66% similarUnverifiedThe lakehouse architecture combines a data lake in open formats (such as Parquet and Iceberg) with the transactional and query capabilities of a database, allowing the same data to be accessed by both the Postgres engine and analytical engines such as Spark and Trino.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1027902API
curl https://kongchang.com/api/v1/knowledge/claims/1027902MCP
get_claim(id=1027902)