You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-7
Original file line number
Diff line number
Diff line change
@@ -84,13 +84,15 @@ kick off from a specific filename or position, use `client.setBinlogFilename(fil
84
84
> `client.connect()` is blocking (meaning that client will listen for events in the current thread).
85
85
`client.connect(timeout)`, on the other hand, spawns a separate thread.
86
86
87
-
> Note difference between MariaDB and MySQL
88
-
```
89
-
BinaryLogClient client = new MariadbBinaryLogClient("hostname", 3306, "username", "password");
90
-
// ... as same as BinaryLogClient
91
-
```
92
-
> `client.setGtidSet(gtid)` meaning that client kick off from a specific gtid, MariaDB also support.
93
-
> `client.setUseSendAnnotateRowsEvent(true)` meaning that client will send annotate rows events(describe the query which caused the row event), and 'false' by default
87
+
88
+
#### MariaDB
89
+
90
+
The stock BinaryLogClient works out of the box with MariaDB but there's two differences;
91
+
92
+
One, MariaDB's GTIDs are different. They're still strings but parse differently.
93
+
Two, Maria can send the ANNOTATE_ROWS events which allows you to recover the SQL used to generate rows in row-based replication.
94
+
95
+
See https://mariadb.com/kb/en/annotate_rows_log_event/ and `client.setUseSendAnnotateRowsEvent(true)`
0 commit comments