Kafkaimporter constraint makes it difficult to use with kafkacdc

The layout of the table that kafkaimporter inserts the data into was designed to be compatible with the layout that the nosqlprotocol uses. If kafkacdc is used as a data transformation tool to read changes from one MariaDB instance and then insert them with kafkaimporter into another MariaDB instance for consumption for the nosqlprotocol, the constraint will block the inserts as it won't be present in the JSON that kafkacdc adds.

A solution to this would be to simply not create the constraint or the _id virtual field as tables created by the nosqlprotocol would already have those.