[
https://issues.apache.org/jira/browse/PHOENIX-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731865#comment-14731865
]
James Taylor commented on PHOENIX-1598:
---------------------------------------
A couple of other advantages of controlling the column qualifier names:
- we could easily support a column rename, as the underlying cq wouldn't change
- we could optimize the lookup of a Cell in a List<Cell> based on some careful
naming (and perhaps some help from HBase). The perf gain would be big for some
queries: see PHOENIX-1940.
> 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)
