From eb92e207c76cb81932b57eafd8cff9fa931bc16e Mon Sep 17 00:00:00 2001 From: Roman Valls Guimera Date: Mon, 23 Oct 2023 15:25:42 +1100 Subject: [PATCH] Refined requirements based on those laid out by @reisingerf on 'ICAv2 migration / OrcaBus focus meeting' document --- skel/rust-api/src/main.rs | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/skel/rust-api/src/main.rs b/skel/rust-api/src/main.rs index 0b9484d6d..5d4711a80 100644 --- a/skel/rust-api/src/main.rs +++ b/skel/rust-api/src/main.rs @@ -21,8 +21,13 @@ use tracing::{info, Level}; /// 1. Listening and ingesting (indexing) file creation events from the different storage backends. /// 2. Querying on file attributes such as name, type of file, creation date, etc... /// 3. Record file provenance (on create, on delete). -/// 4. Record lifecycle status. -/// 5. Checksumming of files is not a requirement at this stage. +/// 4. Record object lifecycle status, i.e: Tier transition, backup to different storage, deletion. +/// 5. Manage object identity, i.e: UUID, path, etc... +/// +/// Non goals: +/// +/// 1. Perform checksumming of files: Too computationally expensive for our file sizes. +/// 2. Link objects/paths to metadata: That would tightly couple filemanager with metadata service. #[tokio::main] async fn main() -> Result<(), Error> {