You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Guanghao Zhang (JIRA)" <ji...@apache.org> on 2017/04/25 08:29:04 UTC

[jira] [Created] (HBASE-17958) Avoid passing cell to ScanQueryMatcher when optimize SEEK to SKIP

Guanghao Zhang created HBASE-17958:
--------------------------------------

             Summary: Avoid passing cell to ScanQueryMatcher when optimize SEEK to SKIP
                 Key: HBASE-17958
                 URL: https://issues.apache.org/jira/browse/HBASE-17958
             Project: HBase
          Issue Type: Bug
            Reporter: Guanghao Zhang


{code}
ScanQueryMatcher.MatchCode qcode = matcher.match(cell);
qcode = optimize(qcode, cell);
{code}
The optimize method may change the MatchCode from SEEK_NEXT_COL/SEEK_NEXT_ROW to SKIP. But it still pass the next cell to ScanQueryMatcher. It will get wrong result when use some filter, etc. ColumnCountGetFilter. It just count the  columns's number. If pass a same column to this filter, the count result will be wrong. So we should avoid passing cell to ScanQueryMatcher when optimize SEEK to SKIP.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)