Protected tables in replication of Galera

[donhardman]

Proposal:

We need to implement a mechanism that will prevent certain tables from being overwritten when we have identical tables on another node in a clustered environment.

The simple process: We create a table on Server A, then we add a new Server B that has the same tables we created on Server A. During synchronization, the contents of those tables on Server B will silently replace the contents on Server A. However, the new requirement is that for certain types of tables, we need to throw an error and prevent synchronization.

The logic is required to protect system tables. We can try to rely on additional metadata in the tables that we can add during table creation or explore other solutions.

Checklist:

^{To be completed by the assignee. Check off tasks that have been completed or are not applicable.}

• Task estimated
• Specification created, reviewed and approved
• Implementation completed
• Tests developed
• Documentation updated
• Documentation proofread
• Changelog updated
• OpenAPI YAML updated and issue created to rebuild clients