VReplication: error out if binlog compression is turned on

[rohit-nayak-ps]

Description

The binlog streamer does not handle the transaction_payload_event, which is sent when binlog compression is used. Currently these events were being silently dropped by VReplication. The copy phase succeeds, but no events are processed while replicating and no error is reported.

With this PR, the VStreamer will error out if it detects binlog compression so that it is reported back to the user. The output of Workflow Show would display something like:

                                        "Pos": "MySQL56/963a4ef5-8333-11eb-a12a-04ed332e05c2:1-42",
					"StopPos": "",
					"State": "Error",
					"DBName": "vt_customer",
					"TransactionTimestamp": 1615554393,
					"TimeUpdated": 1615554417,
					"Message": "Error: vttablet: rpc error: code = Unknown desc = stream (at source tablet) error @ 963a4ef5-8333-11eb-a12a-04ed332e05c2:1-43: VReplication does not handle binlog compression",
					"CopyState": null

See related issue for discussions around this.

Signed-off-by: Rohit Nayak rohit@planetscale.com

Related Issue(s)

• MySQL 8.0 binlog compression does not work with Vitess VReplication #7567

Checklist

• Should this PR be backported?
• Tests were added or are not required
• Documentation was added or is not required

Impacted Areas in Vitess

Components that this PR will affect:

• Query Serving
• VReplication
• Cluster Management
• Build/CI
• VTAdmin

[shlomi-noach]

LGTM even though still in "draft"

[rohit-nayak-ps]

LGTM even though still in "draft"

Thanks! I was waiting for tests to complete and forgot to move it from Draft.