incubator-devlake: [Bug][InnoDB] Setting up InnoDB cluster as Devlake DB

Search before asking

• I had searched in the issues and found no similar issues.

What happened

Hi all , we tried configuring InnoDB cluster as Devlake DB. Met with an issue , few tables dont have primary keys in them . Group Replication has a requirement to have primary key in them .

Error shown -

ERROR: The following tables do not have a Primary Key or equivalent column: 
lake._devlake_locking_stub, lake._tool_teambition_connections, lake._tool_bitbucket_pipeline_steps

Group Replication requires tables to use InnoDB and have a PRIMARY KEY or PRIMARY KEY Equivalent (non-null unique key). Tables that do not follow these requirements will be readable but not updateable when used with Group Replication. If your applications make updates (INSERT, UPDATE or DELETE) to these tables, ensure they use the InnoDB storage engine and have a PRIMARY KEY or PRIMARY KEY Equivalent.
If you can't change the tables structure to include an extra visible key to be used as PRIMARY KEY, you can make use of the INVISIBLE COLUMN feature available since 8.0.23: https://dev.mysql.com/doc/refman/8.0/en/invisible-columns.html

Checking instance configuration...

{
    "status": "error"
}

What do you expect to happen

InnoDB cluster should have recognised devlake mysql instances .

How to reproduce

1. Deploy devlake with a single mysql instance.
2. Deploy mysql-operator using helm-chart. (link)
3. Deploy InnoDB cluster using helm-chart. (link)
4. Try validating mysql instance of step-1 for innodb cluster .(Used - dba.checkInstanceConfiguration(‘Mysql instance’))

Anything else

We can bypass this issue by adding primary key to these tables for now .But it may culminate to become bigger problem when all datas are there on devlake and we try to upgrade Devlake to a higher version .

Version

v0.19.0-beta2

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project’s Code of Conduct