You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ShiXing (Commented) (JIRA)" <ji...@apache.org> on 2012/04/05 12:27:24 UTC

[jira] [Commented] (HBASE-5723) Simple Design of Secondary Index

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

ShiXing commented on HBASE-5723:
--------------------------------

Difficulty and risk
1. During primary table compact, the StoreScanner just read
family.getMaxVersions() versions' data, the old data will be skiped, but the
old data's indices should be deleted, So we must read all version data for
indices' delete, and family.getMaxVersions() version for store's compaction.

Also the timestamp of columns that we want to delete the indices should also have not TimeRange, now it is System.CurrentTimeMillis() - ttl;
                
> Simple Design of Secondary Index
> --------------------------------
>
>                 Key: HBASE-5723
>                 URL: https://issues.apache.org/jira/browse/HBASE-5723
>             Project: HBase
>          Issue Type: New Feature
>          Components: coprocessors
>            Reporter: ShiXing
>            Priority: Minor
>         Attachments: Simple Design of HBase SecondaryIndex.pdf
>
>
> Use coprocessor to create index. And primary tables' compaction to purge the stale data. 
> Attach file is the Design of the Seconday Index.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira