Cannot get binlog info from MariaDB 10.2.x when string length greater than 252

[mia0x75]

MariaDB 10.2.11 w/ CentOS 7.4, go-canal latest git version

table schema:

CREATE TABLE `dt_text` (
  `c` text DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

when string value length less than or equals 252, everything is ok

insert into dt_text values (repeat('1', 252));

and when length greater than 252, go-canal does not print any information.

insert into dt_text values (repeat('1', 252));
insert into dt_text values (repeat('1', 253));
insert into dt_text values (repeat('1', 65535));

[siddontang]

@mia0x75

Can you show me the output information? does go-canal panic?

[mia0x75]

Hi @siddontang,

go-canal is still running, and it prints nothing, it just missing this binlog info.

[siddontang]

How about

insert into dt_text values (repeat('1', 252));
insert into dt_text values (repeat('1', 253));
insert into dt_text values (repeat('1', 65535));
insert into dt_text values (repeat('1', 252));

it just missing this binlog info

What is the mean here?

[mia0x75]

I cannot see any output on go-canal, looks like go-canal miss this change, not sure how go-canal works.

[siddontang]

can you show me the canel output? I am confused what do you say.

[mia0x75]

screen dump attached, thx. The following sample shows 124 characters, not sure if the issue is relevant to charset.

[siddontang]

seem this is not the canal output, do you add the info log by yourself?

[mia0x75]

no, just git clone and compile.

[siddontang]

Do you try insert into dt_text values (repeat('1', 252)); again?

[mia0x75]

it's the same, you can easy to install mariadb to verify.

[mia0x75]

Finally, I find the root cause, the issue is caused by the new system variables introduced in MariaDB 10.2

log_bin_compress & log_bin_compress_min_len

Thus, go-canal cannot process compressed bin log.

[siddontang]

got it @mia0x75

We have not supported the compression yet. You can help us add this if possible.