hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8496) Implement tags and the internals of how a tag should look like
Date Fri, 18 Oct 2013 07:17:48 GMT

    [ https://issues.apache.org/jira/browse/HBASE-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798868#comment-13798868

Anoop Sam John commented on HBASE-8496:

Initially we didnt have ways to make optional tags. Now also if V3 is enabled and writes are
with out any tags, during flush we will write extra 2 bytes of tag length (0) with every KV.
But later during the compaction this also will get removed. Being available this it might
be better to make the default version to 3 so that no need to change explicitely to use tags.
I am +1 for that now.

> 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
>             Fix For: 0.98.0
>         Attachments: Comparison.pdf, HBASE-8496_2.patch, HBASE-8496_3.patch, HBASE-8496_3.patch,
HBASE-8496_3.patch, HBASE-8496_4.patch, HBASE-8496_5.patch, HBASE-8496_6.patch, HBASE-8496.patch,
Performance_report.xlsx, 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

This message was sent by Atlassian JIRA

View raw message