[ 
https://issues.apache.org/jira/browse/HBASE-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anoop Sam John updated HBASE-10454:
-----------------------------------

    Description: 
We always encode tags in case of Prefix tree now and so the code path, while 
decoding, not checking what is there in FileInfo. So functionally no issues now.
If we do HBASE-10453 this change will be very important to make sure BC for old 
files.

We use the file info MAX_TAGS_LEN to know the presence of tags in a file. In 
case of prefix tree we always have tags in files even if all kvs have 0 tags.  
So better we can add this file info into prefix tree encoded HFiles.  Now it 
get missed.

  was:
We always encode tags in case of Prefix tree now and so the code path, while 
decoding, not checking what is there in FileInfo. So functionally no issues now.
If we do HBASE-10453 this change will be very important to make sure BC for old 
files.



> Tags presence file info can be wrong in HFiles when PrefixTree encoding is 
> used
> -------------------------------------------------------------------------------
>
>                 Key: HBASE-10454
>                 URL: https://issues.apache.org/jira/browse/HBASE-10454
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.98.0
>            Reporter: Anoop Sam John
>            Assignee: Anoop Sam John
>            Priority: Minor
>             Fix For: 0.98.0
>
>         Attachments: HBASE-10454.patch, HBASE-10454_V2.patch
>
>
> We always encode tags in case of Prefix tree now and so the code path, while 
> decoding, not checking what is there in FileInfo. So functionally no issues 
> now.
> If we do HBASE-10453 this change will be very important to make sure BC for 
> old files.
> We use the file info MAX_TAGS_LEN to know the presence of tags in a file. In 
> case of prefix tree we always have tags in files even if all kvs have 0 tags. 
>  So better we can add this file info into prefix tree encoded HFiles.  Now it 
> get missed.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to