[
https://issues.apache.org/jira/browse/PHOENIX-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14394161#comment-14394161
]
sunnychen commented on PHOENIX-1736:
------------------------------------
i have a same problem about SingleKeyValueComparisonFilter, i wonder if it does
not work when the column value is null,there is a bug exists in phoenix 3.1,but
it was fixed in phoenix 4.3, what's the solution? could someone told me what's
the problem indeed in phoenix 3.1?
the bug is:
if the table and it's value is as below:
the key is constraint key,which column(name,address,company)is all pk
create sql:
CREATE TABLE stats ( name varchar, address varchar,company varchar, interest
varchar CONSTRAINT pk PRIMARY KEY (name,address,company) );
then upsert the value,the table and its value is now as below:
name address company interest
A1 B1 C1 D1
A2 null C2 D2
A3 null C3 D3
A4 B4 C4 D4
then if you use the sql to query:
select * from stats where address in('B1','B4') and interest='D2';
the query result is :
name address company interest
A2 null C2 D2
so,there is the question,the result is supposed to be null,but the fact is it
has a result,phoenix does not filter the column where the value of address is
null,why???
the bug is solved in 4.3,i wonder if because the hbase defalut filter did not
filter the column where the value is null???
how phoenix 4.3 fix the bug? could you tell me how the bug fix in phoenix 4.3?
thank you very much!
> Use non deprecated APIs where possible
> --------------------------------------
>
> Key: PHOENIX-1736
> URL: https://issues.apache.org/jira/browse/PHOENIX-1736
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: James Taylor
> Fix For: 4.3.1, 4.4.0
>
> Attachments: 1736.patch, 1736_addendum.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
