[
https://issues.apache.org/jira/browse/PHOENIX-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-6220:
---------------------------------
Fix Version/s: 4.16.0
5.1.0
> CREATE INDEX shouldn't ignore IMMUTABLE_STORAGE_SCHEME and
> COLUMN_ENDCODED_BYTES
> ----------------------------------------------------------------------------------
>
> Key: PHOENIX-6220
> URL: https://issues.apache.org/jira/browse/PHOENIX-6220
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Gokcen Iskender
> Assignee: Gokcen Iskender
> Priority: Major
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-6220.4.x.001.patch, PHOENIX-6220.4.x.002.patch,
> PHOENIX-6220.4.x.003.patch
>
>
> IMMUTABLE_STORAGE_SCHEME and COLUMN_ENCODED_BYTES that is specified in CREATE
> INDEX needs to be respected. Today, it is ignored and value is just gotten
> from the parent. Parent table can still use ONE_CELL_PER_COLUMN storage
> scheme. If the parent table is using COLUMN_ENCODED_BYTES=0 (none), we
> recommend using COLUMN_ENCODED_BYTES=2 for the index table by default (can be
> overriden) when SINGLE_CELL storage scheme is used. 2-byte column mapping
> enables to define 65535 columns which should be enough.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
