From f2e22bdb1c2866ce42a65c0260f0d86f0c1b8289 Mon Sep 17 00:00:00 2001 From: Nga Tran Date: Mon, 20 Dec 2021 13:55:07 -0500 Subject: [PATCH] chore: Apply suggestions from code review Co-authored-by: Andrew Lamb --- docs/catalogs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/catalogs.md b/docs/catalogs.md index 95aef51a0b..1c94778435 100644 --- a/docs/catalogs.md +++ b/docs/catalogs.md @@ -9,7 +9,7 @@ Figure 1 below shows the organization of both IOx Catalog and Data. The bottom l [^cat]: This design might be changed in the future to meet other use cases. -Since the catalog is the central information shared to all users of the database, it needs to keep consistent and integral. Each object of the catalog must be locked in either shared or exclusive mod when accessed or modified. Each catalog object also contains information for us to operate the chunk lifecycle, run queries, as well as measure the health of the system. +Since the catalog is the central information shared to all users of the database, it must be kept consistent. Each object of the catalog must be locked in either shared or exclusive mode when accessed or modified. Each catalog object also contains information to operate the chunk lifecycle, run queries, as well as measure the health of the system. **Examples of information for operating the chunk lifecycle** * A chunk includes `LifecycleAction` that keeps track of on-going action of a chunk (e.g. `compacting`, `persisting`) to avoid running the same job on the chunk.