[
https://issues.apache.org/jira/browse/PHOENIX-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482362#comment-14482362
]
sunnychen commented on PHOENIX-1806:
------------------------------------
I am sorry for making such mistake, Thanks for your time~~ ~
> null value will be find out as result when the pk is constraint
> ---------------------------------------------------------------
>
> Key: PHOENIX-1806
> URL: https://issues.apache.org/jira/browse/PHOENIX-1806
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 3.1.0
> Environment: cent os
> Reporter: sunnychen
> Labels: test
> Fix For: 4.3.1
>
>
> 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!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
