Vertica to Databricks

fa source inspect vertica
fa source plan vertica

The Vertica pack inventories SQL objects, projections, external tables, UDx extensions, load and export jobs, resource pools, and consumers. It records deterministic conversion attempts where available and keeps projection design, UDx code, resource policies, COPY extensions, and epoch-specific behavior in owned residue.

Implement movement as a parallel, restartable export with file manifests and a stable epoch or watermark for catch-up. Validate query results, numeric and timestamp behavior, external formats, projection-derived semantics, business scenarios, and representative concurrency independently from conversion.

Airlift freezes the certified object and consumer scope before cutover, enforces authenticated approvals, and records checkpoint, apply-once, verification, or rollback. Modernize to Delta, liquid clustering, Lakeflow, Unity Catalog, and Databricks SQL only after retaining the parity-preserving baseline.

The pack is cataloged pending live route evidence.

Complete developer command sequence

Generate this exact recipe from the installed CLI so the guide and executable surface stay in sync:

fa source recipe vertica
fa source recipe vertica --variant vertica --json > .airlift/vertica-recipe.json

The App is engagement-aware. Vertica appears under Active sources only after the source estate is added to an active engagement. The menu is derived from governed engagement scope; installing Airlift does not expose unrelated source pages.

Every remote mutation below requires --host, --org, authenticated workspace identity, and a stable --idempotency-key. JSON request files contain identifiers, artifact references, and opaque credential references—never passwords, tokens, or connection strings. Run fa <resource> <operation> --help for the current schema and exit semantics.

0. Inspect the source contract

fa source inspect vertica --json > .airlift/vertica-profile.json
fa source plan vertica --variant vertica --json > .airlift/vertica-capability-plan.json

Expected artifacts:

• .airlift/vertica-profile.json
• .airlift/vertica-capability-plan.json

Open Engagements → active engagement in the App. This stage is visible at /engagements after replacing the placeholder ID with the governed engagement ID.

1. Create governed scope and connection references

fa engagement create --file engagement.json --idempotency-key migration-create-v1
fa estate register --file vertica-estate.json --idempotency-key vertica-estate-v1
fa connection register --file vertica-connection.json --idempotency-key vertica-connection-v1
fa engagement update --file vertica-scope.json --idempotency-key vertica-scope-v1
fa engagement preflight <engagement-id>

Expected artifacts:

• Governed engagement
• Source estate
• Opaque connection binding

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id> after replacing the placeholder ID with the governed engagement ID.

2. Assess and accept inventory

fa assessment start --file vertica-assessment-start.json --idempotency-key vertica-assessment-start-v1
fa assessment status <assessment-id> --json
fa assessment record --file vertica-assessment-record.json --idempotency-key vertica-assessment-record-v1
fa assessment accept --file vertica-assessment-accept.json --idempotency-key vertica-assessment-accept-v1
fa inventory list --estate-id <estate-id> --json

Expected artifacts:

• Assessment report reference
• Normalized inventory
• Dependency graph

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/sources/vertica after replacing the placeholder ID with the governed engagement ID.

3. Implement the admitted source adapter

No source-specific executable compiler exists in this release. Continue with assessment, governed work, and an admitted adapter; Airlift does not invent executable output.

Expected artifacts:

• Capability plan and adapter requirements only

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/artifacts after replacing the placeholder ID with the governed engagement ID.

This source is cataloged or assessable but has no source-specific executable compiler in the installed Airlift generation.

4. Convert, move, and remediate

fa plan generate --file vertica-migration-plan.json --idempotency-key vertica-plan-v1
fa conversion batch create --file vertica-batch.json --idempotency-key vertica-batch-v1
fa conversion batch start --file conversion-batch-start.json --idempotency-key conversion-start-v1
fa residue list --engagement-id <engagement-id>
fa transfer plan --file vertica-transfer.json --idempotency-key vertica-transfer-v1
fa transfer run <transfer-id> --idempotency-key transfer-run-v1
fa transfer reconcile <transfer-id> --idempotency-key transfer-reconcile-v1

Expected artifacts:

• Target artifacts
• Residue cases
• Transfer checkpoints
• Reconciliation evidence

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/runs after replacing the placeholder ID with the governed engagement ID.

5. Validate independently and inspect discrepancies

fa validation run --file vertica-validation.json --idempotency-key vertica-validation-v1
fa validation status <validation-execution-id> --json
fa discrepancy list --engagement-id <engagement-id>
fa artifact list --engagement-id <engagement-id>

Expected artifacts:

• Provider run references
• Readiness evidence
• Discrepancies

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/runs after replacing the placeholder ID with the governed engagement ID.

6. Certify, cut over, and export evidence

fa certificate list --object-id <object-id>
fa cutover status <wave-id> --json
fa evidence list --engagement-id <engagement-id>
fa evidence export --file vertica-evidence-export.json --idempotency-key vertica-evidence-export-v1

Expected artifacts:

• Migration certificates
• Cutover evidence
• Content-digested evidence export

Open Engagements → active engagement in the App. This stage is visible at /assurance after replacing the placeholder ID with the governed engagement ID.

Runway executes releases; Experiments owns validation verdicts; Airlift owns migration readiness and cutover policy.

What developers see in the App

The contextual source workspace shows the accepted estate and the factory stages for this engagement. Artifacts displays immutable references, content digests, media types, and provider lineage. Runs displays assessment, conversion, transfer, validation, and deployment executions without treating a provider's success as an Airlift verdict.

View full size

These are automated captures from public synthetic engagements. The source workspace is specific to Vertica; no unrelated source is presented as its migration journey. For sources without an evidence-backed journey, the image demonstrates setup, navigation, and developer entry points only—not a live connection, converted output, or certified migration. No client data, credentials, workspace hostnames, or internal deployment identifiers are embedded in the images.