binlog-listener
v3.5.3
Published
* Row-based binlog replication must be enabled * A mysql user must be created and granted permissions for REPLICATION SLAVE, REPLICATION CLIENT
Downloads
2
Readme
htp-aggregator
Functions to replace replication using binlog watcher and universal data objects
Command Line Options
No options
Default way to run Aggregator Will check if it's the first time being run (sqlite database) and will run a full repush if necessary
Repush Options
--repush all
Calls a script that clears out all rows by productcode from the HTP database then inserts data from a source Pro/EE database
Leaving this option out doesn't do any deleting or repushing of rows
Binlog Options
--start_at_end
--start_now
Starts the binlog watcher at the latest position of the binlog
Tries to get the current Master binlog position and start from there, useful when paired with '--repush all' to start synching rows from the binlog state when
the repush was initiated.
--binlog_position
--binlog_filename
Starts the binlog watcher at a specific position, must be paired with --binlog_filename
Starts the binlog watcher from a specific binlog file, must be paired with --binlog_position
If the given binlog position or the "now" position are invalid, usually due to mistyping or the file no longer exists, the aggregator will typically fail with a
'Packet out of sequence' error then attempt to start at the beginning of the most recent binlog file.
ENV Variables
Passwords should be as Docker secrets in production
PRODUCT
LOG_LEVEL
SOURCE_DATABASE
SOURCE_HOST
SOURCE_USER
SOURCE_PASSWORD
HTP_DATABASE
HTP_HOST
HTP_USER
HTP_PASSWORD
SQLITE_DB_LOCATION
##Pro vs EE Manually change the require in getStartupOptions to the pro or ee plugin