You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org> on 2016/07/26 07:29:20 UTC
[jira] [Commented] (HBASE-11084) Handle deletions and column
tracking using internal filters rather than using DeleteTrackers and
ColumnTrackers
[ https://issues.apache.org/jira/browse/HBASE-11084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393353#comment-15393353 ]
ramkrishna.s.vasudevan commented on HBASE-11084:
------------------------------------------------
May be I can this up and see if it is good to go ahead with what this JIRA intended or do as how SQM is being refactored on a case by case basis.
> Handle deletions and column tracking using internal filters rather than using DeleteTrackers and ColumnTrackers
> ---------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-11084
> URL: https://issues.apache.org/jira/browse/HBASE-11084
> Project: HBase
> Issue Type: Improvement
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Fix For: 2.0.0
>
>
> See HBASE-11054 for discussion.
> Currently the delete tracking is done by DeleteTracker and its subclasses. column tracking and its versions are handled inside the ColumnTrackers and its subclasses.
> This JIRA aims at providing internal filters and attaching them to scans/gets, including minor and major compaction scans so that all the logic of deletes and version counting goes into it rather than having trackers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)