[
https://issues.apache.org/jira/browse/PHOENIX-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14732459#comment-14732459
]
Lars Hofhansl commented on PHOENIX-1598:
----------------------------------------
So what that means for HBase and Phoenix is that every filter, every
coprocessor would need to understand the packed formats, and - for Phoenix -
that expressions can be combined, in the sense that we can get a filed value
once and then use it in multiple expressions (that's in part what makes the
query of PHOENIX-1940 slow, we have to re-retrieve the column value for each
expression over that column)
> 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)
