[jira] [Updated] (CARBONDATA-2088) It better using ‘timeseries_cube’ instead of ‘preaggregate’ for timeseries pre-aggregate table

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Updated] (CARBONDATA-2088) It better using ‘timeseries_cube’ instead of ‘preaggregate’ for timeseries pre-aggregate table

Akash R Nilugal (Jira)

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

xubo245 updated CARBONDATA-2088:
--------------------------------
    Summary: It better using ‘timeseries_cube’ instead of ‘preaggregate’ for timeseries pre-aggregate table   (was: It maybe better to name it to ‘timeseries’ instead of ‘preaggregate’ for timeseries pre-aggregate table )

> It better using ‘timeseries_cube’ instead of ‘preaggregate’ for timeseries pre-aggregate table
> -----------------------------------------------------------------------------------------------
>
>                 Key: CARBONDATA-2088
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-2088
>             Project: CarbonData
>          Issue Type: Improvement
>          Components: core, spark-integration
>    Affects Versions: 1.3.0
>            Reporter: xubo245
>            Assignee: xubo245
>            Priority: Major
>             Fix For: 1.3.0
>
>
>  it maybe better to name it to ‘timeseries’ instead of ‘preaggregate’ for timeseries pre-aggregate table,because:
> {code:java}
> 1. It is a cube that understands the dimension hierarchy of time, it is not a simple preaggregate table
> 2. This datamap creates multiple pre-aggregate tables, not just one. And DROP DATAMAP command will drop multiple table too.
> {code}
> and change
> {code:java}
> timeseries.eventTime  =>eventTime
> timeseries.hierarchy =>hierarchy
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)