Bifrost Document

Version 1.6.x

Bifrost ---- A heterogeneous middleware which can synchronize MySQL binlog data To Redis,MongoDB,ClickHouse...

Privileges

GRANT

GRANT SELECT, SHOW DATABASES, SUPER, REPLICATION SLAVE, EVENT ON . TO ‘xxtest’@‘%’

RDS cloud product database cloud product permissions, may not be according to MySQL open source permissions, please confirm by yourself whether there is sufficient permissions

The following SQL permissions need to be executed

SELECT COLUMN_NAME,COLUMN_DEFAULT,IS_NULLABLE,COLUMN_TYPE,COLUMN_KEY,EXTRA,COLUMN_COMMENT,DATA_TYPE,NUMERIC_PRECISION,NUMERIC_SCALE FROM information_schema.columns WHERE TABLE_SCHEMA = ? AND TABLE_NAME = ?

SELECT COLUMN_NAME,COLUMN_KEY,COLUMN_TYPE,CHARACTER_SET_NAME,COLLATION_NAME,NUMERIC_SCALE,EXTRA,COLUMN_DEFAULT,DATA_TYPE,CHARACTER_OCTET_LENGTH FROM information_schema.columns WHERE table_schema= ? AND table_name= ? ORDER BY ORDINAL_POSITION ASC

SELECT SCHEMA_NAME FROM information_schema.SCHEMATA

SELECT TABLE_NAME,TABLE_TYPE FROM information_schema.TABLES WHERE TABLE_SCHEMA = ?

SHOW GLOBAL VARIABLES LIKE ‘BINLOG_CHECKSUM’

SHOW MASTER STATUS

SHOW VARIABLES LIKE ‘server_id’

SHOW VARIABLES LIKE ‘binlog_format’

SELECT connection_id()

SELECT TIME,STATE FROM information_schema.PROCESSLIST WHERE ID = ?’

KILL $connectionId

 

Notes

If it is a cloud product such as RDS, please make sure that you have ** permission to listen on Binlog,** permission to KILL the current account connection **, and ** permission to SET

When you add a data source checkPrivilege, you will not be able to detect the data source checkPrivilege. When you add a data source checkPrivilege, you will not be able to detect the data source checkPrivilege

Last updated on 30 Jan 2021
Edit on GitHub