Jacob Isaac created PHOENIX-5477:
------------------------------------
Summary: Dropping an include column when column families are
specified causes multiple EMPTY_COLUMNS to be created in the index table.
Key: PHOENIX-5477
URL: https://issues.apache.org/jira/browse/PHOENIX-5477
Project: Phoenix
Issue Type: Bug
Affects Versions: 4.15.0
Reporter: Jacob Isaac
Steps to reproduce :-
CREATE TABLE IF NOT EXISTS "TEST_ENTITY"."T_T000105"(OID CHAR(15) NOT NULL,KP
CHAR(3) NOT NULL,ID CHAR(15) NOT NULL,A.COL1 VARCHAR,A.COL2 VARCHAR,A.COL3
VARCHAR CONSTRAINT pk PRIMARY KEY (OID,KP,ID))
MULTI_TENANT=true,COLUMN_ENCODED_BYTES=0;
CREATE INDEX IF NOT EXISTS "IDX_T_T000105" ON "TEST_ENTITY"."T_T000105"(COL1)
INCLUDE (COL3);
UPSERT INTO "TEST_ENTITY"."T_T000105" (OID,KP,ID,COL1,COL2,COL3)
VALUES('o1','0EC','1','a','b','c');
scan "TEST_ENTITY.IDX_T_T000105"
Values before dropping column -
ROW
COLUMN+CELL
o1 a\x000EC1
column=A:A:COL3, timestamp=1568578538617, value=c
o1 a\x000EC1
column=A:_0, timestamp=1568578538617, value=\x01
1 row(s) in 0.0350 seconds
ALTER TABLE TEST_ENTITY.T_T000105 DROP COLUMN COL3;
Values after dropping column -
ROW
COLUMN+CELL
o1 a\x000EC1
column=0:_0, timestamp=1568578538617, value=
o1 a\x000EC1
column=A:_0, timestamp=1568578538617, value=\x01
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
