Details
-
Sub-task
-
Status: In Progress
-
Major
-
Resolution: Unresolved
-
HDFS-7240
-
None
-
None
Description
A new version of a key is effectively overwriting some consecutive range of bytes in the entire key offset range. For each version, we need to keep exactly what the range is in order for the IO vector to work.
Currently, since we only write from the start (offset = 0), so offset range of a version is only up to the key data size field when the version gets committed. But currently we only keep one single key data size variable.(see KeyManagerImpl#commitKey). We need to know the corresponding key data size for each version. This JIRA is to the tracking of offset range for each version.
Attachments
Attachments
Issue Links
- Dependent
-
HDFS-12989 Ozone: Container : Add key versioning support-4
- In Progress
- relates to
-
HDFS-12925 Ozone: Container : Add key versioning support-2
- Patch Available