You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2017/10/30 23:13:01 UTC

[jira] [Resolved] (HBASE-11131) Improve essential column family handling when more than one SingleColumnValueFilter is involved

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

Ted Yu resolved HBASE-11131.
----------------------------
    Resolution: Won't Fix

Stale issue

> Improve essential column family handling when more than one SingleColumnValueFilter is involved
> -----------------------------------------------------------------------------------------------
>
>                 Key: HBASE-11131
>                 URL: https://issues.apache.org/jira/browse/HBASE-11131
>             Project: HBase
>          Issue Type: Task
>          Components: Filters
>            Reporter: Ted Yu
>            Priority: Minor
>
> Currently, SingleColumnValueFilter determines essential column family based on:
> {code}
>   public boolean isFamilyEssential(byte[] name) {
>     return !this.filterIfMissing || Bytes.equals(name, this.columnFamily);
> {code}
> When more than one SingleColumnValueFilter is used through FilterList, some optimization can be done.
> e.g. when they are chained by Operator.MUST_PASS_ALL, the second and subsequent SingleColumnValueFilter can declare to be non-essential.
> This way their evaluation would depend on the outcome of the first SingleColumnValueFilter.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)