Molt Fetch

by cockroachdb6c96c6394a61No license4 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 2 months ago

Guide for using molt fetch to migrate data from PostgreSQL, MySQL, Oracle, or MSSQL to CockroachDB. Use when running molt fetch commands, configuring storage backends, handling fetch failures/resumption, or chaining fetch with verify.

Instructions onlyDevOps & Cloud
AI-generated overview

Guides running molt fetch to bulk-migrate PostgreSQL, MySQL, Oracle, or MSSQL data into CockroachDB.

What it does
This skill is a usage guide for the molt fetch command, which bulk-migrates data from PostgreSQL, MySQL, Oracle, or MSSQL into CockroachDB. It documents command structure, storage backend options, table handling modes, import modes, key flags, source-specific prerequisites, resume workflows, and error recovery. It produces guidance and example commands rather than files or code.
When to use it
Use it when running molt fetch commands, choosing storage backends, configuring table handling or import modes, resuming failed migrations, or chaining fetch with verify.
Requirements
Requires the molt binary and network access to the source database and CockroachDB target. Oracle sources additionally require CGO and Oracle Instant Client; cloud storage backends need credentials or implicit auth. Ships no scripts, only a flags reference document.

molt fetch

Bulk data migration from source databases (PostgreSQL, MySQL, Oracle, MSSQL) to CockroachDB.

Basic Structure

bash
molt fetch \  --source "<source-conn>" \  --target "<crdb-conn>" \  --bucket-path "s3://bucket/prefix"   # or --direct-copy or --local-path  [options]

Storage Backends (pick one)

OptionWhen to use
--bucket-path "s3://..."AWS S3 (also gs:// for GCS, azure:// for Azure)
--direct-copyNo intermediate storage; fastest for accessible networks
--local-path "/tmp/molt" + --local-path-listen-addr "0.0.0.0:9005"CRDB must reach the listen addr

Cloud auth: pass --use-implicit-auth for IAM/ADC/managed identity, or set AWS_ACCESS_KEY_ID/GOOGLE_APPLICATION_CREDENTIALS env vars.

Table Handling (--table-handling)

ValueBehavior
none (default)Append to existing tables
drop-on-target-and-recreateDrop + recreate from source schema; enables auto schema creation. Destroys existing target tables and their data, so use only on fresh or empty targets
truncate-if-existsTruncate before loading; errors if table missing

Import Mode

IMPORT INTO (default): Table goes OFFLINE during load. Highest throughput.

COPY FROM (--use-copy): Table stays ONLINE. Use with --direct-copy. Cannot use compression.

bash
# Zero-downtime loadmolt fetch --source "..." --target "..." --direct-copy --use-copy

Key Flags

bash
# Filtering--table-filter "customers|orders"      # POSIX regex for tables to include--table-exclusion-filter "temp_.*"     # exclude pattern--schema-filter "public"               # PostgreSQL only
# Performance--table-concurrency 4                  # parallel tables (default: 4)--export-concurrency 4                 # export threads (default: 4)--row-batch-size 100000                # rows per SELECT (default: 100k)
# Schema--type-map-file "types.json"           # custom type mappings--transformations-file "transforms.json"  # column exclusions, table aliases
# Logging--log-file "migration.log"             # or "stdout"--logging debug                        # info (default), debug, trace--metrics-listen-addr "0.0.0.0:3030"  # Prometheus scrape endpoint

Source-Specific Prerequisites

MySQL: GTID mode required (gtid_mode=ON, enforce_gtid_consistency=ON). ONLY_FULL_GROUP_BY must be off. Or use --ignore-replication-check.

Oracle: Binary must be built with CGO_ENABLED=1 -tags="cgo source_all". Oracle Instant Client in LD_LIBRARY_PATH.

PostgreSQL: Replication privileges needed, or --ignore-replication-check.

Common Workflows

1. Full migration with schema creation

drop-on-target-and-recreate drops any existing target tables first; run this only against a fresh or empty target.

bash
molt fetch \  --source "postgresql://<user>:<password>@pg:5432/db" \  --target "postgresql://root@crdb:26257/db" \  --bucket-path "s3://mybucket/migration" \  --table-handling drop-on-target-and-recreate \  --table-filter "customers|orders|payments" \  --log-file migration.log

2. Resume after failure

bash
# List available continuation tokensmolt fetch tokens --fetch-id "abc-123" --target "postgresql://root@crdb:26257/db"
# Resume all failed tablesmolt fetch \  --source "..." --target "..." \  --bucket-path "s3://mybucket/migration" \  --fetch-id "abc-123" \  --non-interactive

Error Recovery

ErrorCauseFix
"GTID-based replication not enabled"MySQL missing GTIDEnable gtid_mode=ON or add --ignore-replication-check
"Column mismatch"Schema divergedFix target schema manually or use --type-map-file
Silent IMPORT INTOCockroachDB import runningSHOW JOBS on CRDB to check progress
"timestamp in the future"Docker/Mac clock driftSync clocks between hosts

Gotchas

  • COPY mode: cannot use --compression gzip; must use --compression none (or omit, default is none with copy)
  • Table is offline during IMPORT INTO — use --use-copy for zero downtime
  • Schema changes between runs require starting from scratch
  • --fetch-id continuation tokens live in the target's exceptions table
  • For MySQL, --ignore-replication-check skips GTID validation but replication-dependent features won't work
  • After fetch, run molt verify to confirm data integrity

See flags reference [blocked] for the full flag list.

Source and attribution

Source:cockroachdb/claude-plugininskills/cockroachdb-onboarding-and-migrations/molt-fetchat commit6c96c63

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal