phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-1598) encode column names to save space
Date Wed, 16 Sep 2015 00:11:45 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746548#comment-14746548
] 

Lars Hofhansl commented on PHOENIX-1598:
----------------------------------------

Talked to [~giacomotaylor]. I get what he wants now.

We can already pass a List to HRegionScannerImpl.nextRaw. So we could pass a custom implementation
of List and either passed in a dense list with all positions pre-populated with null and fill
in slots as HBase adds them (with the assumption that a column name can imply its ordinal
position) or we could have a List backed by a HashMap (which would be reasonably cheap for
Integer keys).

There are some wrinkles in HBase trunk now, with interesting logic looping over all cells
and calling cloneToCell on them, we'd have to implement everything in the passed List implementation
to support all of these operations.


> 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)

Mime
View raw message