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
Describe the bug
We use the org.flowable:flowable-event-registry:7.1.0 dependency. We currently have version 6.8.0, DB schema also has the same version. We tried upgrading to 7.1.0, upgrade failed because flowable-event-registry-7.1.0.jar!/org/flowable/eventregistry/db/upgrade/flowable.all.upgradestep.7100.to.7101.eventregistry.sql tries to drop a table that does not exist.
Expected behavior
The upgrade happens without errors. The SQL command should contain IF EXISTS clause. Note: there still might be another problem, maybe the table should be present.
The text was updated successfully, but these errors were encountered:
Hi! Yes, I have checked it now. We don't do any kind of that magic on the DB level, we have a single datasource. We have not enabled/disabled event registry.
Hi, when you don't have the FLW_EV_DATABASECHANGELOG and FLW_EV_DATABASECHANGELOGLOCK tables mentioned in that sql file, it means that you were not running the event registry engine before. Can you try to explicitly disable the event registry with the flowable.eventregistry.enabled=false property? Or can you share your project setup so we can check how you are running Flowable exactly?
Describe the bug
We use the org.flowable:flowable-event-registry:7.1.0 dependency. We currently have version 6.8.0, DB schema also has the same version. We tried upgrading to 7.1.0, upgrade failed because flowable-event-registry-7.1.0.jar!/org/flowable/eventregistry/db/upgrade/flowable.all.upgradestep.7100.to.7101.eventregistry.sql tries to drop a table that does not exist.
Expected behavior
The upgrade happens without errors. The SQL command should contain IF EXISTS clause. Note: there still might be another problem, maybe the table should be present.
The text was updated successfully, but these errors were encountered: