chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Yang (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CHUKWA-336) TableCreator will not create table if the date is more than 1 month in the past.
Date Sat, 31 Mar 2012 03:43:21 GMT

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

Eric Yang resolved CHUKWA-336.
------------------------------

    Resolution: Won't Fix

We no longer support SQL database partitioning.  This is not an issue anymore.
                
> TableCreator will not create table if the date is more than 1 month in the past.
> --------------------------------------------------------------------------------
>
>                 Key: CHUKWA-336
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-336
>             Project: Chukwa
>          Issue Type: Bug
>          Components: Data Processors
>    Affects Versions: 0.1.2, 0.2.0, 0.3.0
>         Environment: Redhat EL 5.1, Java 6
>            Reporter: Eric Yang
>             Fix For: 0.5.0
>
>
> The current algorithm for pin point data on the time partition works as follow:
> If the selected time resolution is less than 24 hours, use weekly table.
> If the selected time resolution is less than 7 days, use monthly table.
> If the selected time resolution is less than 30 days, use quarterly table.
> If the selected time resolution is less than 91 days, use yearly table.
> If the selected time resolution is less than 365 days, use decade table.
> If the selected time resolution is 2x partition in the past, fall back to lower resolution
table (weekly to monthly, monthly to quarterly, etc)
> Base on those rules, let's say if I select 12 hours data for 05-15-2009, and the current
date is 06-28-2009, the system will attempt to locate data on quarterly table.  Those rules
operate fine for charting.  For data loading, the rules also applies except the last rule
for fall back.
> This has been implemented as two methods in DatabaseConfig, findTableNameForCharts and
findTableName.  findTableName should should not have the last rule for fall back, but the
current code have last rule applied.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message