This is an automated email from the ASF dual-hosted git repository. vinish pushed a commit to branch 590-RFC-CatalogSync in repository https://gitbox.apache.org/repos/asf/incubator-xtable.git
commit 41c67b6496da3802699d7250257752ec98efd109 Author: Vinish Reddy <[email protected]> AuthorDate: Wed Dec 18 23:22:00 2024 -0800 Rebase with latest rfc template --- assets/images/catalog_sync_flow.jpg | Bin 130344 -> 131331 bytes rfc/rfc-1/rfc-1.md | 10 +++++----- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/assets/images/catalog_sync_flow.jpg b/assets/images/catalog_sync_flow.jpg index 237dc909..660d8d73 100644 Binary files a/assets/images/catalog_sync_flow.jpg and b/assets/images/catalog_sync_flow.jpg differ diff --git a/rfc/rfc-1/rfc-1.md b/rfc/rfc-1/rfc-1.md index 1f6a8310..8b350a4a 100644 --- a/rfc/rfc-1/rfc-1.md +++ b/rfc/rfc-1/rfc-1.md @@ -122,20 +122,20 @@ datasets: tableName: "target-tableName-2" ``` -## Overview of the CatalogSync process +## Overview of the `RunCatalogSync` process  ## Rollout/Adoption Plan +- Are there any breaking changes as part of this new feature/functionality ? + - In `SyncResult` status has been refactored to tableFormatSyncStatus for clarity. - What impact (if any) will there be on existing users? - - Nope, this is a new functionality being added to synchronize tables across catalogs. Existing XTable users can still use the table format sync using RunSync without any problems. -- If we are changing behavior how will we phase out the older behavior? + - No on existing users, this is a new functionality being added to synchronize tables across catalogs. Existing XTable users can still use the table format sync in `RunSync` without any issues. +- If we are changing behavior how will we phase out the older behavior? When will we remove the existing behavior ? - N/A - If we need special migration tools, describe them here. - N/A -- When will we remove the existing behavior - - N/A ## Test Plan
