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
A recent update in the persistence-commons-postgresql Flyway sql migration scripts introduced a possible issue when migrating from an old installation of Data Index to a newer version. The problem lies on data-index-storage-postgresql depending on persitence-commons-postgresql to index Domain objects. Both modules rely in Flyway to initialize their DB and they use different versioning strategy in the Flyway migrations having persitence-commons-postgresql using a lower version number in the Flyway scripts (1.5) than data-index-storage-postgresql (1.45).
Recently a PR introduced a new .sql in persistence-commons using the module versioning number which introduced a conflict in Flyway while validating the intalled migrations.
A recent update in the
persistence-commons-postgresql
Flyway sql migration scripts introduced a possible issue when migrating from an old installation of Data Index to a newer version. The problem lies ondata-index-storage-postgresql
depending onpersitence-commons-postgresql
to index Domain objects. Both modules rely in Flyway to initialize their DB and they use different versioning strategy in the Flyway migrations havingpersitence-commons-postgresql
using a lower version number in the Flyway scripts (1.5
) thandata-index-storage-postgresql
(1.45
).Recently a PR introduced a new .sql in persistence-commons using the module versioning number which introduced a conflict in Flyway while validating the intalled migrations.
Zulip chat: https://kie.zulipchat.com/#narrow/channel/382044-kogito-dev/topic/Data.20Index.20database.20broken/near/497424089
apache/incubator-kie-kogito-apps#2139
The text was updated successfully, but these errors were encountered: