HolyLow commented on issue #1372: URL: https://github.com/apache/kvrocks/issues/1372#issuecomment-1732781698
@git-hulk I see this issue in the roadmap, and as it seems that no one is working on it (because this issue is troublesome and dirty...?), could you assign it to me? Currently I only have some unclear thoughts on this topic. I think to check the data encoding compatibility, we are supposed to: 1. Write the raw data in different version's encoding (use the RocksDB api directly and bypass the kvrocks api); 2. Then read the data with the current version's kvrocks api to check if the data is readable and the data semantic is correct. But still, I am not sure of the proper workflow, or how far we should go. Maybe you could kindly refer me to some existing projects' "data encoding checking" mechanism/code to shed me some light, if you happen to know. I would try to find some material myself as well. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
