What is causing this error?

An Adobe Commerce Architect is investigating a case where some EAV product attributes are no longer updated.

• The catalog is composed of 20.000 products with 100 attributes each.

• The product updates are run by recurring Adobe commerce imports that happen multiple times a day.

• The Architect finds an error in the logs that indicates an integrity constraint while trying to insert row with id 2147483647.

What is causing this error?
A . Magento framework uses INSERT on DUPLICATE, which leads to reaching the max limit of the increment of the column.
B . Integrity constraints were dropped after upgrading to the latest version, and the integrity checks were missed.
C . EAV attribute import uses REPLACE, which leads to reaching the max limit of the increment of the column

View Answer

Answer: C

Explanation:

EAV attribute import uses the REPLACE statement, which deletes and inserts a new row with the same primary key value. This causes the auto-increment column to increase by one for each row, even if the row already exists. If the auto-increment column reaches its maximum value, which is 2147483647 for a signed INT, then any further REPLACE statement will fail with an integrity constraint violation error.

Reference: EAV and extension attributes | Magento 2 Developer Documentation GitHub – techdivision/import-attribute: This library provides the functionality for the Magento 2 import of EAV attributes

Data integrity in JSON (B) when replacing EAV – Stack Overflow