Skip to content

Commit 9e19267

Browse files
committed
update README
1 parent 2ae2eb8 commit 9e19267

File tree

1 file changed

+9
-7
lines changed

1 file changed

+9
-7
lines changed

README.md

+9-7
Original file line numberDiff line numberDiff line change
@@ -84,13 +84,15 @@ kick off from a specific filename or position, use `client.setBinlogFilename(fil
8484
> `client.connect()` is blocking (meaning that client will listen for events in the current thread).
8585
`client.connect(timeout)`, on the other hand, spawns a separate thread.
8686

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)`
9496

9597
#### Controlling event deserialization
9698

0 commit comments

Comments
 (0)