[PHOENIX-6220] CREATE INDEX shouldn't ignore IMMUTABLE_STORAGE_SCHEME and COLUMN_ENDCODED_BYTES

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 5.1.0, 4.16.0
• Assignee: Gokcen Iskender
• Reporter: Gokcen Iskender
• Created: 11/Nov/20 21:28
• Updated: 28/Jan/21 04:49
• Resolved: 15/Jan/21 18:42

Description

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.

Issue Links

• is a clone of: PHOENIX-6219 GlobalIndexChecker should work for index:SINGLE_CELL_ARRAY_WITH_OFFSETS and data:ONE_CELL_PER_COLUMN
• links to: GitHub Pull Request #963