No project should be affected in their daily operations and no action is required, this is a purely informational message about an upcoming change.
From May 3rd we will begin gradually turn on strict primary key checking in all applications. This will cause all components writing to Storage to fail if the primary key on the table does not match the one set in the component's configuration.
Previously the primary key was set when the table was created and was not checked any further.
We recently started monitoring primary key mismatches and tried to fix them automatically - the component executor tried to modify the primary key on the table so that it would match the configuration. A few situations arose where it couldn't be fixed automatically:
- New primary key contained columns not present in the table
- New primary key could not be set as there were duplicate values in the new primary key columns
- Several configurations in the project were changing the primary key back and forth
We have contacted all projects affected by these issues and resolved them. We will continue to monitor this situation closely until we switch on the strict checking.