Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
- Enable encryption for a TiFlash deployment using the next-gen proxy.
- Write data with a latest-release-tikv / latest CSE version so the encryption metadata contains data keys generated by that version.
- Let TiFlash read or ingest the generated data.
2. What did you expect to see? (Required)
TiFlash should read the encrypted data normally.
3. What did you see instead (Required)
TiFlash may panic while reading the data key from encryption metadata because the data key id used by the latest CSE metadata does not match the id inferred by the older TiFlash proxy code.
4. What is your TiFlash version? (Required)
current master 63cff9a6e02ff2d70655f738c69a9dc4398c354f
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
TiFlash should read the encrypted data normally.
3. What did you see instead (Required)
TiFlash may panic while reading the data key from encryption metadata because the data key id used by the latest CSE metadata does not match the id inferred by the older TiFlash proxy code.
4. What is your TiFlash version? (Required)
current master
63cff9a6e02ff2d70655f738c69a9dc4398c354f