[ https://issues.apache.org/jira/browse/PHOENIX-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261375#comment-16261375 ]
Thomas D'Silva commented on PHOENIX-2565: ----------------------------------------- [~shehzaadn] We has discussed implementing a different storage format that uses a bitset to efficiently determine if a value was null or missing . If we did this, then we could use this storage format for multi-tenant tables with views. > Store data for immutable tables in single KeyValue > -------------------------------------------------- > > Key: PHOENIX-2565 > URL: https://issues.apache.org/jira/browse/PHOENIX-2565 > Project: Phoenix > Issue Type: Improvement > Reporter: James Taylor > Assignee: Thomas D'Silva > Fix For: 4.10.0 > > Attachments: PHOENIX-2565-v2.patch, PHOENIX-2565-wip.patch, > PHOENIX-2565.patch > > > Since an immutable table (i.e. declared with IMMUTABLE_ROWS=true) will never > update a column value, it'd be more efficient to store all column values for > a row in a single KeyValue. We could use the existing format we have for > variable length arrays. > For backward compatibility, we'd need to support the current mechanism. Also, > you'd no longer be allowed to transition an existing table to/from being > immutable. I think the best approach would be to introduce a new IMMUTABLE > keyword and use it like this: > {code} > CREATE IMMUTABLE TABLE ... > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)