Skip to content

V2 roadmap (post-V1 feature backlog) #16

Description

@ihistand

Umbrella for the post-V1 backlog. Full context + per-item notes live in SQLAnvil/docs v2_roadmap.md. Split an item into its own (sub-)issue when it's picked up.

  • MySQL / MariaDB adapter — shipped in 1.5.0 (PR feat: MySQL/MariaDB adapter #34). Deferred follow-ups (mysql: {} options block, materialized views, COMMENT metadata, MySQL source introspect) tracked in MySQL/MariaDB adapter — deferred follow-ups #35all shipped by 1.19.0; MySQL/MariaDB adapter — deferred follow-ups #35 closed.
  • Import/export at the warehouse edges — shipped incrementally: type: "export" (1.8.0, BigQuery EXPORT DATA + Postgres/Supabase via the DuckDB bridge), type: "import" (1.12.0, gs://, s3:// incl. Supabase Storage, local), cross-warehouse DB↔DB reads via named connections: (FDW bridge + runner-extract: keyless BigQuery 1.14–1.15, cross-project billingProject 1.13.0, MySQL/MariaDB sources 1.18.0), with sqlanvil introspect scaffolding the type translation. Python script actions (1.20.0, Python script actions (type: "python") — execution-time staging/glue steps in the DAG #48) cover the fetch/staging step in-DAG. Remaining gap: Azure Blob object storage (no azure:// scheme yet) — split into its own issue if demand shows.
  • Dataform → SQLAnvil conversion tool — design complete, now unified with interactive init as the New-Project wizard (2026-07-06): one setup flow with two paths — start fresh (Q&A over the 1.21 init scaffold) or convert a Dataform project (OSS sqlanvil migrate-dataform converter + Cloud onboarding flow). Spec in the private planning repo. Not yet built; tracking issues to be opened when scheduled.
  • Interactive sqlanvil init (Q&A scaffolding) — folded into the New-Project wizard design (see the conversion-tool item above): sqlanvil init --interactive asks fresh-vs-convert and drives either the 1.21 sample scaffold or the Dataform converter. 1.21.0 already shipped the generated sample project this builds on.
  • --environment (named dev/staging/prod environments) — shipped in 1.7.0.
  • Pre-run SQL validation — sqlanvil validate + run --dry-run shipped in 1.9.0 (EXPLAIN-validates the whole DAG in a throwaway shadow schema; PASS/FAIL/BLOCKED), later extended to MySQL, BigQuery (shadow dataset), and python script actions (env/syntax check, 1.20.0).

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestroadmapPost-V1 feature backlog

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions