Historical Sync CLI Guide
Using Datacoral CLI historical syncs can be triggered. Here is the list of commands that can be used for it.
Historical sync command
Picking the right backfill for your usecase
Backfills are typically carried out in case of data discrepancy between source and destination.
It is extremely critical that the correct type of backfill is chosen based on the type of discrepency.
Below is the list of 4 types of backfills and the scnearios in which each of them should be used -
- FULL backfill - When either the table that needs to be backfilled is pretty small or if FULL backfill was never successfully carried out in the past
- PARTIAL_TIME_WINDOW backfill - When there is a small time window for which data did not sync AND the source table is pretty large to carry out full backfill
- PARTIAL_PK_LIST backfill - When there are just a handfull of primary keys which are not correctly synced to the destination
- COLUMN backfill - When the issue is only there with one or more columns of the table and the source table is pretty large to carry out full backfill
Trigger partial backfill/partial historical sync for the connector
Create a control file
The control yaml file needs be of the below format with multiple loadunits and multiple types.
note
Backfill and historical sync are used interchangeably and mean the same.
Trigger partial backfill
Example
Trigger full historical sync for all loadunits in the connector
Historical syncs for all the tables in a connector
Example
Output
Trigger full historical sync for specific loadunits in the connector
Historical syncs for specific tables in a connector
Example
Output
Get status for all loadunits in a connector
Example
Output
Get status for specific loadunit
Example
Output
Get detailed historical sync status of all loadunits
Example
Output
Get detailed sync status of specific loadunits
Example
Output