dlg99 commented on pull request #2730: URL: https://github.com/apache/bookkeeper/pull/2730#issuecomment-857140165
@sijie The full BP that goes through the value add, I'll be happy to expand on specific points if I described them too briefly. I am also open to suggestions how to achieve specifically described usecases better in a different manner. Specifically how to achieve GDPR case for "right to be forgotten" in pulsar when short and long lived data is mixed at the same bookie cluster. The plan is to have this functionality disabled by default. When enabled, any payload modifications should happen before digest computation. I understand the sentiment regarding immutability, but whatever does modify the payload should happen 1. reversibly (typically, I cannot predict all usecases) 2. as planned by the author and administrator of the BL cluster. HDDs supposed to save whatever the user saves to them yet there are usecases for [self-encrypting drives](https://en.wikipedia.org/wiki/Hardware-based_full_disk_encryption#Hard_disk_drive_FDE). This case is similar IMO. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
