[
https://issues.apache.org/jira/browse/HBASE-19824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16342907#comment-16342907
]
Reid Chan commented on HBASE-19824:
-----------------------------------
I found a description from cloudera's documentation:
bq. If the specified column is not found, all the columns of that row will be
emitted. If the column is found and the comparison with the comparator returns
true, all the columns of the row will be emitted. If the condition fails, the
row will not be emitted.
Does it mean if a column match, and the comparator return false, then all the
columns of the row will be kept? *If this is how it is designed*, i think
[[email protected]]'s query result is right, since 'f1:a1:a1' match, entire
row 'r1' including 'f1:b1:b2' should be kept.
My presumption(not right maybe) is only the match column and value should be
kept, confirmation and discussion needed. @all watching
> SingleColumnValueFilter returns wrong result when used in shell command
> -----------------------------------------------------------------------
>
> Key: HBASE-19824
> URL: https://issues.apache.org/jira/browse/HBASE-19824
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha-4
> Reporter: Ted Yu
> Assignee: Reid Chan
> Priority: Major
>
> There are two cells in table t1:
> {code}
> ROW COLUMN+CELL
> r1 column=f1:a1,
> timestamp=1516313683984, value=a2
> r1 column=f1:b1,
> timestamp=1516313700744, value=b2
> {code}
> When SingleColumnValueFilter is used in shell command, no filtering was done:
> {code}
> hbase(main):022:0> scan 't1', {FILTER => "SingleColumnValueFilter('f1', 'a1',
> =, 'binary:a2')"}
> ROW COLUMN+CELL
> r1 column=f1:a1,
> timestamp=1516313683984, value=a2
> r1 column=f1:b1,
> timestamp=1516313700744, value=b2
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
