Skip to content

Latest commit

 

History

History
33 lines (25 loc) · 846 Bytes

File metadata and controls

33 lines (25 loc) · 846 Bytes

Databricks over S3 Exports

This variation keeps the Rust exporter and S3 publish path as the source of truth, then lets Databricks consume the published parquet snapshots.

flowchart LR
  C[Convex]
  X[convex-sync run]
  S3[staging/current in S3]
  UC[Unity Catalog external location]
  V[stable SQL views]
  C --> X
  X --> S3
  S3 --> UC
  UC --> V
Loading

Contents

  • terraform/unity_catalog_s3_external_location/: storage credential, external location, grants
  • sql/register_staging_views.sql.tmpl: stable read_files(...) view template

Operational Rule

The published staging/current prefix must be covered by a Unity Catalog external location before the view sync is applied.

Recommended entrypoint:

just databricks-sync-staging-views --warehouse-id <warehouse-id> --bucket <bucket> --prefix <prefix>