You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chukwa.apache.org by "Eric Yang (JIRA)" <ji...@apache.org> on 2011/09/04 04:35:09 UTC

[jira] [Updated] (CHUKWA-596) Chukwa HBase storage should scan for column from most recent time instead of starting time

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

Eric Yang updated CHUKWA-596:
-----------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

I just committed this.

> Chukwa HBase storage should scan for column from most recent time instead of starting time
> ------------------------------------------------------------------------------------------
>
>                 Key: CHUKWA-596
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-596
>             Project: Chukwa
>          Issue Type: Improvement
>          Components: User Interface
>    Affects Versions: 0.5.0
>         Environment: Java 6, Mac OS X
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>             Fix For: 0.5.0
>
>         Attachments: CHUKWA-596.patch
>
>
> HICC UI access REST API with a time range.  i.e. Last 24 hours.  Current ChukwaHBaseStore API is scanning for column names from start time to end time.  With full scan disabled, then it is fetching a single row from the starting time to present the columns existed for that time period.  Columne name retrieval does not work very well for cluster that has just been setup because there is no data in the specified start time, but there is often data for specified end time.  I recommend to change the column name retrieval api to use end time as indicator.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira