[
https://issues.apache.org/jira/browse/PHOENIX-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17234000#comment-17234000
]
ASF GitHub Bot commented on PHOENIX-6220:
-----------------------------------------
gokceni commented on pull request #963:
URL: https://github.com/apache/phoenix/pull/963#issuecomment-729222821
Merged
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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
> 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)
