Skip to main content

Set JDBC sync mode

POST 
/platform/jobs/jdbc/:jobId/sync-mode

Migrate between full_load, incremental and incremental_with_qualify with validation and state management. Set target_load_type. Incremental modes need incremental_column_name and incremental_column_type; qualify also needs primary_keys. Optional force addresses warnings, not invalid configuration.

Example: incremental deduplication​

{
  "target_load_type": "incremental_with_qualify",
  "incremental_column_name": "updated_at",
  "incremental_column_type": "timestamp with time zone",
  "primary_keys": ["id"]
}

State transitions​

Source guidance initializes state when moving from full load to incremental, resets state when returning to full load, and says to preserve the bookmark when switching between incremental variants. Moving to or from qualify updates the deduplication DAG task. The next execution uses the new configuration.

Source success fields include status, message and migration_details with target type, state_action and warnings. Validation failures include missing incremental fields/primary keys, unsupported datatypes and a non-JDBC job. Use Allowed JDBC datatypes for engine-specific spelling. The imported request schema does not fully express conditional business rules; optional fields are not unnecessary in every target mode.

Request​

Responses​

Sync mode updated