Steve T created PHOENIX-2709:
--------------------------------
Summary: SELECT Bug With LIMIT Work-Around
Key: PHOENIX-2709
URL: https://issues.apache.org/jira/browse/PHOENIX-2709
Project: Phoenix
Issue Type: Bug
Affects Versions: 4.6.0
Reporter: Steve T
Priority: Minor
I came across a 4.6.0 query that I could not make work unless I add a "limit"
to the end, where it should be totally unnecessary.
{color:blue}
{{select * from BUGGY where F1=1 and F3 is null}}
{color}
results in no records found
{color:blue}
{{select * from BUGGY where F1=1 and F3 is null limit 999}}
{color}
results (correctly) in one record found
I think it's a bug where Phoenix gets confused about my HBase columns and
views. Here's how to set up the table to duplicate my problem:
{{{color:blue}
CREATE TABLE BUGGY (
F1 INTEGER NOT NULL,
A.F2 INTEGER,
B.F3 INTEGER,
CONSTRAINT my_pk PRIMARY KEY (F1));
create view if not exists BUGGY_A as select * from BUGGY;
alter view BUGGY_A drop column if exists F3;
create view if not exists BUGGY_B as select * from BUGGY;
alter view BUGGY_B drop column if exists F2;
upsert into BUGGY(F1) values (1)
{color}}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
