Apply database schema updates automatically in every deployment
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 35/100
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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
- 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.
- 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. - 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
- The tool. Liquibase already defines the chain in
sql/changelog.xml, and local databases already carry itsdatabasechangelogtable. Flyway, or the plain psql loop that local development runs today, are the alternatives. - 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.
- 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
- Lingua principale
- Scala
- Stelle
- 333
- Fork
- 202
- Merge medio
- 3g 11h
- PR unite (30g)
- 185
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di apache/texera
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
addOperator returns an error but still adds the operatorForse già presa @sunny-kavixo l’ha presa 5 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
apache/texera#9121 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Failed tool calls are marked as succeeded (isError is always false)Forse già presa @oliarmak-web l’ha presa 14 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
apache/texera#9120 · 8 commenti · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
apache/texera#8682 · 5 commenti ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di apache/texera
Issue simili
-
? - Needs Triage bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
NVIDIA/cudf-spark#16937 ·
I maintainer di solito rispondono entro 1 giorno
-
LFST not-issued-store count truncation can incorrectly clear strictShouldWaitForse già presa @weidingliu l’ha presa oggi. Apertamodule: memory type: bug/reported
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
OpenXiangShan/XiangShan#6974 · 1 commento · 1 assegnatario ·
I maintainer di solito rispondono entro 3 giorni
-
bug indigo
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
PurpleKingdomGames/indigoengine#300 · 1 commento ·
-
JavaReservoirSampleOperator returns the whole input when the dataset size is unknownForse già presa @sasmith-14 l’ha presa 2 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
apache/wayang#884 · 3 commenti ·
I maintainer di solito rispondono entro 2 giorni
-
AI Generated CI/CD ⚒️ Flaky-tests 🐦 python 🐍
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
valkey-io/valkey-glide#7722 ·
I maintainer di solito rispondono entro 1 giorno