[
https://issues.apache.org/jira/browse/PHOENIX-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15783551#comment-15783551
]
Thomas D'Silva edited comment on PHOENIX-2565 at 12/28/16 7:29 PM:
-------------------------------------------------------------------
[[email protected]]
For your use case, are all the columns of the same fixed width datatype? If so
we can use the fixed width array serialization which doesn't need to store
array offsets.
If the columns are fixed length but of different data types, since the offsets
are the same for all of the rows, we don't need to serialize the offset array
for every row.
was (Author: tdsilva):
[[email protected]]
For your use case, are all the columns of the same fixed length datatype? If so
we can use the fixed width array serialization which doesn't need to store
array offsets.
If the columns are fixed length but of different data types, since the offsets
are the same for all of the rows, we don't need to serialize them for every
row. But we would need to figure out where to store the offset array.
> 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
> 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.3.4#6332)
