Skip to content

Impact of Data Integrity #4841

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.

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

Open
psumu opened this issue May 20, 2025 · 0 comments
Open

Impact of Data Integrity #4841

psumu opened this issue May 20, 2025 · 0 comments
Labels
status: waiting-for-triage Issues that we did not analyse yet

Comments

@psumu
Copy link

psumu commented May 20, 2025

Hi Spring-Batch Team,

We recently migrated from Spring Batch 4.0 to 5.0 and adopted a new database schema, which includes three additional columns and the exclusion of a few existing ones. Please find the below screenshot. In sporadic rollback scenarios, we may need to revert to the older code base immediately(code base which contain spring batch 4.0 JPA Query on database schema). Given the schema changes, how can we ensure that the records added under the new schema remain compatible with the previous version?

For Example:

Image

Considering the above screenshot, after rolling back the codebase (which contains Spring Batch 4.0 JPA queries on the database schema), how can we ensure the retrieval of PARAMETER_VALUE for further processing of those records?

@psumu psumu added the status: waiting-for-triage Issues that we did not analyse yet label May 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: waiting-for-triage Issues that we did not analyse yet
Projects
None yet
Development

No branches or pull requests

1 participant