We’ve recently upgraded from 7.7 to 7.10, the migration went mostly smooth.
But MySql throws a warning after this upgrade
Duplicate index 'ACT_IDX_CASE_EXE_CASE_INST' defined on the table 'test-platform.ACT_RU_CASE_EXECUTION'. This is deprecated and will be disallowed in a future release
Which references ACT_IDX_CASE_EXE_CASE_INST which gets created in the 7.7.8 to 7.7.9_2 sql migration.
It looks like this index overlaps ACT_FK_CASE_EXE_CASE_INST which in our case was created during the initial setup.
Does anyone perhaps have an idea about this warning?
@aravindhrs Thank you for your reply.
That’s where I got the database migration steps from.
If we look in the mysql_engine_7.10.0.sql (in the create folder) it contains the following
-- https://app.camunda.com/jira/browse/CAM-9165
create index ACT_IDX_CASE_EXE_CASE_INST on ACT_RU_CASE_EXECUTION(CASE_INST_ID_);
-- create foreign key constraints on ACT_RU_CASE_EXECUTION --
alter table ACT_RU_CASE_EXECUTION
add constraint ACT_FK_CASE_EXE_CASE_INST
foreign key (CASE_INST_ID_)
references ACT_RU_CASE_EXECUTION(ID_) on delete cascade on update cascade;
Which seems to be both the constraints that MySql gave me a warning about listed right next to each other in the Camunda schema setup.
Drop the existing index and try.