From 0f16a38b159a8cffa2336ec2513160e49429059c Mon Sep 17 00:00:00 2001 From: Angela-CMU Date: Wed, 31 Jan 2024 10:18:14 -0500 Subject: [PATCH] Remove multi-versioning in design --- doc/design_doc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/design_doc.md b/doc/design_doc.md index 7ecb141..3399da3 100644 --- a/doc/design_doc.md +++ b/doc/design_doc.md @@ -11,7 +11,7 @@ The goal of this project is to design and implement a **Catalog Service** for an We follow the logic model described below. The input of our service comes from execution engine and I/O service. And we will provide metadata to planner and scheduler. ![system architecture](./assets/system-architecture.png) ### Data Model -We adhere to the Iceberg data model, arranging tables based on namespaces, with each table uniquely identified by its name. Our goal is to enable multi-versioning, facilitating point-in-time queries and allowing for queries at a specific historical version of the table. +We adhere to the Iceberg data model, arranging tables based on namespaces, with each table uniquely identified by its name. For every table in the catalog, there is an associated metadata file. This file contains a collection of manifests, each of which references the table's information at different points in time. The manifest file is an in-memory, non-persistent component that gets recreated based on on-disk files during service restarts. (If it is not frequently updated, we could dump it to disk every time we update it)