You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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?
The text was updated successfully, but these errors were encountered:
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:
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?
The text was updated successfully, but these errors were encountered: