You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Vishal Khandelwal (JIRA)" <ji...@apache.org> on 2018/12/21 12:20:00 UTC
[jira] [Created] (PHOENIX-5077) DATA_BLOCK_ENCODING data encoding
for local index should not be allowed
Vishal Khandelwal created PHOENIX-5077:
------------------------------------------
Summary: DATA_BLOCK_ENCODING data encoding for local index should not be allowed
Key: PHOENIX-5077
URL: https://issues.apache.org/jira/browse/PHOENIX-5077
Project: Phoenix
Issue Type: Bug
Reporter: Vishal Khandelwal
{code:java}
CREATE TABLE TEST1.TBL (key1 INTEGER NOT NULL, v1 FLOAT, v2 FLOAT, v3 INTEGER CONSTRAINT PK PRIMARY KEY(key1) )DATA_BLOCK_ENCODING=ROW_INDEX_V1;
CREATE LOCAL INDEX TEST1TBL_INDEX1 ON TEST1.TBL (key1, v2);
CREATE LOCAL INDEX TEST1TBL_INDEX3 ON TEST1.TBL (key1, v3) DATA_BLOCK_ENCODING=ROW_INDEX_V1;{code}
For Global index whenever DATA_BLOCK_ENCODING is used on index, phoenix put the same on new index & hbase table where as incase of local indexes all indexes are part of L#0 so different index can't have different DATA_BLOCK_ENCODING. It should restricted and DATA_BLOCK_ENCODING should be same as data table
In current scenario every new encoding would change the encoding of L#0 which might not be give expected results.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)