[
https://issues.apache.org/jira/browse/PHOENIX-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14733140#comment-14733140
]
stack commented on PHOENIX-1598:
--------------------------------
bq. ... would it be possible to put an interface in place in HBase that would
control the population of the List<Cell> given a Cell?
Sure. Would be good to see how much better the ordinal lookup would be than
binary search. These are fixed-size keys I presume.
The STRUCT sounds like C* supercolumns since deprecated
http://stackoverflow.com/questions/11915255/why-are-super-columns-in-cassandra-no-longer-favoured
It should be possible to plug in other block encodings now (We have a bunch of
alternate implementations currently)
> 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)
