gracecluvohio opened a new issue, #4400: URL: https://github.com/apache/texera/issues/4400
### Task Summary When PRs that change the database schema are merged, they break developers' local instances because the schemas become out of sync. Currently, the author must notify all developers and provide instructions on how to apply the update, becoming a potential source of miscommunication and inconsistent environments. This ultimately slows down development. Recent PRs #4250 and #4323 tried to address this by sending email notifications on a DDL change, such as below: <img width="500" height="" alt="Image" src="https://github.com/user-attachments/assets/5bb4d309-623f-493a-9c57-2f10cb6baa14"; /> However, this still requires all developers to run the sql update file every time such a PR is merged. This is not sustainable as more updates accumulate over time and more developers join the project. To address this, I propose we use Liquibase to automate database migrations and updates to the schema. With Liquibase integrated into the development workflow, schema updates would be applied automatically every time developers start their local instances, ensuring consistency across environments and reducing manual coordination overhead. ### Priority P2 – Medium ### Task Type - [ ] Code Implementation - [ ] Documentation - [ ] Refactor / Cleanup - [ ] Testing / QA - [x] DevOps / Deployment -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
