Skip to content

JDBC: Handle schema evolution #2714

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

JDBC: Handle schema evolution #2714

wants to merge 1 commit into from
+260 −68

Conversation

singhpk234
Copy link
Contributor

@singhpk234 singhpk234 commented Sep 30, 2025 •
edited
Loading

About the change

  1. This PR introduces a new static helper which based on the schema can give back the columns for the Entity Table
  2. Handle the cases where location_without_scheme doesn't exist, v1 tables
  3. Enables running the metastore manager suite with all version of schema to detect v1, v2, v3 schema changes faster
  4. Adds a prod readiness check to not enable OPTIMIZE sibling check becuase it may bet that we migrated from v1 to v2 schema and the column location_without_scheme has missing data

solves

@github-project-automation github-project-automation bot moved this to PRs In Progress in Basic Kanban Board Sep 30, 2025
@singhpk234 singhpk234 added this to the 1.2.0 milestone Sep 30, 2025
@singhpk234 singhpk234 changed the title Persistence: Handle schema evolution JDBC: Handle schema evolution Sep 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@flyrain flyrain Awaiting requested review from flyrain

@dimas-b dimas-b Awaiting requested review from dimas-b

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
1.2.0
Development

Successfully merging this pull request may close these issues.
1 participant
@singhpk234