[
https://issues.apache.org/jira/browse/PHOENIX-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14742966#comment-14742966
]
James Taylor commented on PHOENIX-1598:
---------------------------------------
HBase couldn't know the right ordinal position. It'd be the typical design
pattern:
- Create new interface that would abstract List<Cell> access (initial creation,
adds and searches).
- Scan would include an optional class name that would be in implementor of new
interface.
- Default implementation would be existing behavior: just add to the list based
on the Comparator and use a binary search for getting.
- Clients could override by setting class name in Scan (or some other
config-based mechanism) to allow positional access for clients able to control
position through column qualifier name.
> 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)
