-
Notifications
You must be signed in to change notification settings - Fork 583
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
Task re-launch fails when using BOOT3 and Oracle #5534
Comments
Hi @MattiJH ,
Thanks |
Hi @onobc
I checked |
Those 2 files should be functionally kept in sync. The ones under https://github.com/spring-cloud/spring-cloud-dataflow/blob/main/spring-cloud-dataflow-server-core/src/main/resources/schemas are static and provided as a convenience for when users are not using Flyways (see here for details). The ones under https://github.com/spring-cloud/spring-cloud-dataflow/blob/main/spring-cloud-dataflow-server-core/src/main/java/org/springframework/cloud/dataflow/server/db/migration are dynamic and used by Flyway. They should be kept functionally in sync. It looks like we introduced a regression here. Thank you for finding and reporting this. As a workaround, you can replace it w/ the previous definition (in the commit link above). Otherwise, we will get it fixed asap and into the next 2.11.2 release. We need to beef up our Oracle testing in the Boot3 area as well. |
I set |
Glad that got you going @MattiJH . Can you tell me more about this
Could you please send a screenshot of what you are seeing when this happens? Thank you |
Thanks @MattiJH - we will give this a deeper look. So far I have not been able to reproduce it. |
This commit introduces an Oracle schema migration that updates the BOOT3_BATCH_JOB_EXECUTION_PARAMS table to use the newer Batch5 parameter columns. Resolves spring-cloud#5534
* Fix columns in BOOT3_BATCH_JOB_EXECUTION_PARAMS This commit introduces an Oracle schema migration that updates the BOOT3_BATCH_JOB_EXECUTION_PARAMS table to use the newer Batch5 parameter columns. Resolves #5534 * Drop and re-add the `IDENTIFYING` column (keep same order as before)
We are starting use SCDF to run and configure our task in our project.
During testing we noticed an issue when every single task launch after the first one fails with same error.
We get the same error from SCDF, when checking Job Executions.
Also launch builder does not show itself after the first launch. (Free-text works)
By doing cleanup or by removing pods manually everything starts working correctly, until we launch our task again.
Version
SCDF version: 1.21.1, with oracle db driver: ojdbc11-21.9.0.0 (classpath extend using these instructions)
Spring Batch: 5.0.3
Spring cloud task: 3.0.3
Task stacktrace
SCDF stacktrace
SCDF launch builder
The text was updated successfully, but these errors were encountered: