Apply database schema updates automatically in every deployment

Offen
#9,484 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Refactoring
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
github-actions, helm, kubernetes, postgresql, scala
Bereich
ci-cd, database, devops

Rechercherichtung

Start with sql/changelog.xml, sql/updates/, and sql/texera_ddl.sql, then trace how local development, single-node deployment, Kubernetes, and CI initialize the database. The issue identifies the migration-tool choice, Kubernetes execution point, and baseline for databases without history as open decisions. Done means every deployment runs one migration step before services start, and CI detects when applying updates to the last release schema does not match texera_ddl.sql.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Task Summary

The resource unification in #9395 changes tables that every deployment already holds, one step at a time, so each step has to reach an existing database by itself. Today it does not. A schema change is written twice, as a numbered file in sql/updates/ listed in sql/changelog.xml and as an edit to sql/texera_ddl.sql, but only local development applies the numbered files on its own. Single-node and Kubernetes load texera_ddl.sql when the database is first created and never again, so upgrading an existing deployment means applying each new update by hand. CI loads only texera_ddl.sql, so nothing checks that the two copies agree.

Local development already follows a sound rule: a new database starts from texera_ddl.sql and records every update as applied, and an existing database applies the updates it lacks, in order. This task makes that rule the one migration step of every deployment, and checks it in CI.

Before
flowchart TB
  ddl["sql/texera_ddl.sql<br/>the whole schema, edited by hand"]
  upd["sql/updates/23.sql … 52.sql<br/>listed in sql/changelog.xml"]
  ld["Local development<br/>applies pending updates"]
  sn["Single-node<br/>updates by hand"]
  k8s["Kubernetes<br/>updates by hand"]
  ci["CI<br/>never runs an update"]
  ddl -- "new database" --> ld
  ddl -- "new database" --> sn
  ddl -- "new database" --> k8s
  ddl -- "every job" --> ci
  upd --> ld
After
flowchart TB
  ddl["sql/texera_ddl.sql<br/>for a new database"]
  upd["sql/updates/NN.sql<br/>one ordered chain"]
  step["One migration step<br/>runs before the services start"]
  ld["Local development"]
  sn["Single-node"]
  k8s["Kubernetes"]
  ci["CI<br/>also checks: last release's schema<br/>+ new updates = texera_ddl.sql"]
  ddl --> step
  upd --> step
  step --> ld
  step --> sn
  step --> k8s
  step --> ci
Scope
  1. One migration step. Single-node, Kubernetes, local development and CI run the same step before the services start, so an upgrade needs no SQL by hand.
  2. A check in CI. The updates, applied to the schema of the last release, must give the same schema as texera_ddl.sql, so a pull request that changes one without the other fails.
  3. One documented rule. The contributor guide says in one place what to write for a schema change.

This task changes no table. Removing the unused scripts 01 to 22 is #7702.

Discussion Points
  1. The tool. Liquibase already defines the chain in sql/changelog.xml, and local databases already carry its databasechangelog table. Flyway, or the plain psql loop that local development runs today, are the alternatives.
  2. Where the step runs on Kubernetes. A Helm hook job runs once per upgrade. An init container runs at every start of a service, and needs a lock so that two replicas do not migrate at once.
  3. Deployments with no history. A single-node or Kubernetes database has never recorded which updates it holds. The first run needs a baseline, either stated by the deployer or detected from the schema.

Done when an existing single-node or Kubernetes deployment upgrades to a release with a new update without anyone running SQL by hand, and CI fails when an update and texera_ddl.sql disagree.

Related: #4400, #6194.

Task Type
  • Refactor / Cleanup
  • DevOps / Deployment / CI
  • Testing / QA
  • Documentation
  • Performance
  • Other
Vorherrschende Sprache
Scala
Sterne
333
Forks
202
Ø Merge
3 T. 11 Std.
Gemergte PRs (30 T.)
185

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus apache/texera

Alle Issues in apache/texera

Ähnliche Issues

Weitere Issues zu Scala

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.