[
https://issues.apache.org/jira/browse/PHOENIX-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14742920#comment-14742920
]
Lars Hofhansl commented on PHOENIX-1598:
----------------------------------------
The point I am not seeing is that how would HBase know the right ordinal
position to populate the fixed size array without searching for the column
(since any column may or not exist for any given row)
If the columns have known names (1,2,3,..., or C1,C2,C3, ..., etc), then it can
be done... But then I would argue that a client can (and should?) do that at no
loss of performance or generality.
> 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)
