[
https://issues.apache.org/jira/browse/HBASE-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729855#comment-13729855
]
ramkrishna.s.vasudevan commented on HBASE-8496:
-----------------------------------------------
>>Pls note that we would not be persisting any tag related information on the
>>HFileBlock.
HFileBlock would not be modified in terms of what is persisted. In the recent
patch that we have worked up on we are just enclosing some of the state
variables into a POJO.
So specifically for tags there are no modifications on HfileBlock. So there is
no need for subclassing HFileBlock or add a new version to the hfileblock.
>>Based on the Encoding/Decoding context state the Encoder and decoding logic
>>of the algos would handle tags.
In the previous version of the patches the includeMemstoreTS and the
includeTags created changes to the interface apis. So as to avoid this we
enclosed these things inside the Context. Iin the recent patches the context
would have the POJO mentioned above).
So from the context we would be able to get the various decision points like to
include tags or not, includememstoreTS or not.
The encoding apis carry the context but the actual seekers that does the actual
decoding does not use contexts. So we have made changes such that the encoding
logic and the seekers use the context related objects.
> 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
> Affects Versions: 0.98.0, 0.95.2
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Priority: Critical
> Attachments: Comparison.pdf, HBASE-8496_2.patch, HBASE-8496.patch,
> Tag design.pdf, Tag design_updated.pdf, Tag_In_KV_Buffer_For_reference.patch
>
>
> 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
