[PHOENIX-2455] Partial results for a query when PHOENIX-2194 is applied

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.7.0
• Assignee: James R. Taylor
• Reporter: Ankit Singhal
• Created: 25/Nov/15 20:17
• Updated: 14/Dec/15 20:58
• Resolved: 14/Dec/15 19:55

Description

Hi giacomotaylor,

can you please look into the below test case, why it is failing after applying PHOENIX-2194

drop table test;
CREATE TABLE IF NOT EXISTS Test
 (col1 VARCHAR,  
 col2 VARCHAR,  
 col3 VARCHAR,  
 col4 UNSIGNED_LONG NOT NULL,   
 CONSTRAINT pk  
 PRIMARY KEY (col1,col2,col3,col4));

upsert into test values('a','b','',1);
upsert into test values('e.f','b','',1);
upsert into test values('f.g','b','',1);
upsert into test values('g.h','b','',1);
upsert into test values('f','b','',1);
upsert into test values('h.e','b','',1);


SELECT  col1, col2, col3, col4 FROM test WHERE (col1 IN ('a','e','f','g','h')) AND col2 = 'b' AND col4 >= 0 AND col4 < 2 ;

expected(AND getting without PHOENIX-2194);-

COL1	COL2	COL3	COL4
a	b		1
f	b		1

Getting with PHOENIX-2194(Which is partial).

COL1	COL2	COL3	COL4
a	b		1

Issue Links

• relates to: PHOENIX-2194 order by should not require all PK fields with = constraint