[
https://issues.apache.org/jira/browse/PHOENIX-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14732479#comment-14732479
]
James Taylor commented on PHOENIX-1598:
---------------------------------------
IMO, we should separate the dense/sparse discussion from the column name
discussion. The former is the STRUCT idea (PHOENIX-477) and the later is this
JIRA.
For the column name optimization, would it be possible to put an interface in
place in HBase that would control the population of the List<Cell> given a
Cell? HBase would just use it's normal/standard implementation, and other
clients (like Phoenix) could have an implementation that would leverage the
above column qualifier -> position optimization.
An alternative to the STRUCT idea would be to have a block encoding in HBase
that was better for dense data (HBASE-12883).
I think we need to explore these HBase options, as this will give more bang for
the buck by doing it at the lower level. We just don't have the bandwidth in
Phoenix to do all of these things there.
> encode column names to save space
> ----------------------------------
>
> Key: PHOENIX-1598
> URL: https://issues.apache.org/jira/browse/PHOENIX-1598
> Project: Phoenix
> Issue Type: Improvement
> Reporter: noam bulvik
>
> when creating table using phoenix DDL replace the column names that the user
> give with shorter names to save space. the user will still the full name is
> his select statements and will get them in the result set but under the hood
> the infra will translate the names to their sorter version.
> example:
> when creating table with my_column_1, my_column_2 ... the table will be
> created with a as first column , b as the second one etc'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
