Provide suitable error message if user attempts "jump" upgrade (ex: 1.0.0->1.3.0 for SeismicAcquisitionSurvey)
I tried this by mistake. Service response was clean and did not indicate any problem.
However converted record remained the same except schema version showed 1.3.0.
Suggest that you issue meaningful error message and abort the conversion.
Note from @vikashoode -
Currently, the schema upgrade lacks the capability to directly transition from version 1.0.0 to 1.3.0.
To address this, we are developing a feature that will chain upgrade operations, allowing a step-by-step progression, such as 1.0.0 to 1.1.0, then 1.1.0 to 1.2.0, and finally 1.2.0 to 1.3.0. This approach involves temporarily storing intermediate states in a cache or temporary memory. However, this feature is still a work in progress. I still need to programmatically determine the number of progression steps involved and handle potential errors in the intermediate upgrade processes.
For the time being, a manual process is required:
Upgrade from 1.0.0 to 1.1.0. Upgrade from 1.1.0 to 1.2.0. Upgrade from 1.2.0 to 1.3.0.
This interim solution will be replaced by the chained upgrade feature once it is fully implemented and tested.
Regards, Vikas