hubio-sync sync

Run an incremental data synchronization.

Status: 🚧 Pending Implementation

This command is defined but not yet fully implemented. The interface is documented here for planning purposes.

Synopsis

hubio-sync sync --source <name> --destination <name> [flags]

Description

The sync command performs an incremental synchronization, transferring only new or changed data since the last sync. This is more efficient than full migration for ongoing data replication.

Flags

Flag	Short	Required	Description
`--source`	`-s`	Yes	Source configuration name
`--destination`	`-d`	Yes	Destination configuration name
`--config`	`-c`	No	Configuration file path

Planned Features

When fully implemented, this command will support:

Incremental change detection (timestamp, ID-based)
Change Data Capture (CDC) integration
State persistence between runs
Conflict resolution strategies
Deduplication
Real-time streaming mode

Examples

Basic Incremental Sync

hubio-sync sync --source mysql-prod --destination s3-datalake

With Custom Config

hubio-sync sync \
  --source postgres-orders \
  --destination bigquery-analytics \
  --config /path/to/config.toml

Current Output

Running the command currently shows:

Starting incremental sync from 'mysql-prod' to 's3-datalake'
Sync implementation pending (Phase 5)

Difference from migrate

Aspect	`migrate`	`sync`
Data scope	Full dataset	Changed data only
Use case	Initial load, one-time	Ongoing replication
State	Stateless	Tracks last sync position
Speed	Slower (full scan)	Faster (incremental)