phoenix-dev mailing list archives

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

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

James Taylor commented on PHOENIX-1598:
---------------------------------------

We'd store the mapping in our metadata a table (SYSTEM.CATALOG). We already
use this during query compilation so there'd be no additional overhead.
Space savings (disk & memory) could be potentially large, (2-3x) especially
when values are small and column names are long as the bulk of the space
used by a KeyValue is from the column qualifier. And the potential
2.5x performance gain
(see PHOENIX-1940) if we can know the Cell position in the List<Cell>
result from a scan without doing a binary search would be the biggest win.


> 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