[
https://issues.apache.org/jira/browse/HBASE-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13710653#comment-13710653
]
ramkrishna.s.vasudevan commented on HBASE-8496:
-----------------------------------------------
Thinking on the compatibility issues once we have Codec to work with HFiles,
If we introduce V3 without changing the HFileBlock headers it would be easy for
us to make the Codec to work in trunk.
As the plan is to write the Codec used in the HFile header, for those files
written using existing HFileV2 and the HFileV3(tags) we would need to read the
Hfile header and as we come to know that there is no codec used in these
hfiles, find out the major version of these files.
If it is V2 instantiate a default codec that works with KVs(without tags) and
if the major version is V3 instantiate a default codec that works with KVs(with
tags). By this way we solve the problem of compatibility.
Later V2 and V3 would ideally become the same code and we can decide on the
version later.
Ideally speaking, the codec way of encoding and decoding the KVs is the best
way of doing things. But because of all said above we need a simpler and viable
solution and that is why we would like to move ahead with HFile V3
This V3 way of implementation can make the Tags as an optional feature and so
not risky.
Considering the above facts we would like to propose that going with HFileV3
would help us have tags in 0.96.
> Implement tags and the internals of how a tag should look like
> --------------------------------------------------------------
>
> Key: HBASE-8496
> URL: https://issues.apache.org/jira/browse/HBASE-8496
> Project: HBase
> Issue Type: New Feature
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Fix For: 0.98.0
>
> Attachments: Tag design.pdf
>
>
> The intent of this JIRA comes from HBASE-7897.
> This would help us to decide on the structure and format of how the tags
> should look like.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
