-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Row content being logged as part of CDC ErrMessageTooLarge logging #9031
Labels
affects-6.5
affects-7.1
area/ticdc
Issues or PRs related to TiCDC.
severity/minor
type/bug
The issue is confirmed as a bug.
Comments
darraes
added
area/ticdc
Issues or PRs related to TiCDC.
type/bug
The issue is confirmed as a bug.
labels
May 23, 2023
/area ticdc |
/severity major |
/severity minor |
/remove-label may-affects-7.1 |
ti-chi-bot
bot
added
affects-6.5
affects-7.1
and removed
may-affects-7.1
may-affects-6.5
labels
May 25, 2023
/remove-label may-affects-6.1 |
17 tasks
/remove-label affects-6.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-6.5
affects-7.1
area/ticdc
Issues or PRs related to TiCDC.
severity/minor
type/bug
The issue is confirmed as a bug.
What did you do?
If a message is too large, both the Canal JSON and the Open Protocol encoders are logging the full message.
You can see the issue in 3 files:
canal_json_row_event_encoder.go:347
canal_json_tx_event_encoder.go:64
canal_json_row_event_encoder.go:69
What did you expect to see?
The message itself (the row data) should not be printed in logs as this is a PII violation
What did you see instead?
The content of the row
Versions of the cluster
Upstream TiDB cluster version (execute
SELECT tidb_version();
in a MySQL client):(paste TiDB cluster version here)
Upstream TiKV version (execute
tikv-server --version
):(paste TiKV version here)
TiCDC version (execute
cdc version
):v7.0.0
The text was updated successfully, but these errors were encountered: