phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samarth Jain (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-3575) Store column counters at global view level
Date Sat, 07 Jan 2017 00:11:58 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Samarth Jain updated PHOENIX-3575:
----------------------------------
    Issue Type: Sub-task  (was: Task)
        Parent: PHOENIX-1598

> Store column counters at global view level
> ------------------------------------------
>
>                 Key: PHOENIX-3575
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3575
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Samarth Jain
>
> Today we store the column qualifier counters at the base table level. Views created on
the table use this common pool of counters. When views are altered i.e. when columns are added
to them, it is likely that the qualifiers allocated to views are not contiguous. This makes
the data for views sparse which prevents us from taking advantage of encoding strategies.
See discussion on PHOENIX-2565. There could be use cases where the user defines a global view
and then child views are defined on that global view. By storing the counter at global view
level, child views will be allocated a relatively contiguous set of column qualifiers (especially
if they are not modified after the initial CREATE VIEW call).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message