Are Spring Batch 3 database structure changes compatible with Spring Batch 2? -


we migrated spring batch 2.1.7 spring batch 3.0.6, got jboss startup error:

org.springframework.jdbc.badsqlgrammarexception: preparedstatementcallback; bad sql grammar [select e.job_execution_id, e.start_time, e.end_time, e.status, e.exit_code, e.exit_message, e.create_time, e.last_updated, e.version, e.job_instance_id, e.job_configuration_location batch_job_execution e, batch_job_instance e.job_instance_id=i.job_instance_id , i.job_name=? , e.end_time null order e.job_execution_id desc]; nested exception java.sql.sqlsyntaxerrorexception: ora-00904: "e"."job_configuration_location": invalid identifier

...which apparently caused spring batch 3 auto-migration, in spring batch 3 has table structure changes spring batch 2.

to things moving forward, using create table script our developer team found in 1 of spring batch jars, our dba team wrote script update (instead of create) tables, since need job history. working far, here our issue:

we can't migrate our systems forward spring batch 3. have leave older ones in spring batch 2 while.

are these spring batch 3 table structure changes backward compatible spring batch 2?

they appear analysis our dba team , our batch run results far, i'm asking if intentional spring, i.e. when spring altered table structure purposes of spring batch 3, did intentionally make backward compatible?

so far appear compatible, want make sure there isn't subtle difference break our system badly down not-often-used logic path, i.e. @ statement execution time (vs jboss startup time).

ben ethridge

they not backwards compatible. way job parameters stored different. migration scripts did not remove old columns (just added net new). doesn't mean couldn't come schema works both versions (it looks that's have), our intent, identified breaking change when added non-identifying parameters.


Comments

Popular posts from this blog

Is there a better way to structure post methods in Class Based Views -

performance - Why is XCHG reg, reg a 3 micro-op instruction on modern Intel architectures? -

jquery - Responsive Navbar with Sub Navbar -