chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ari Rabkin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CHUKWA-569) Add an option to speed up graph_explorer.jsp in fetching Column Name and Row Name
Date Tue, 28 Dec 2010 22:19:45 GMT

    [ https://issues.apache.org/jira/browse/CHUKWA-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975656#action_12975656
] 

Ari Rabkin commented on CHUKWA-569:
-----------------------------------

I think that assumption is usually a safe one -- particularly if the scan only covers, say,
the most recent 20 rows.

What about explicitly keeping a separate metadata table, either in HBase or in Zookeeper?

> Add an option to speed up graph_explorer.jsp in fetching Column Name and Row Name
> ---------------------------------------------------------------------------------
>
>                 Key: CHUKWA-569
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-569
>             Project: Chukwa
>          Issue Type: Improvement
>          Components: User Interface
>         Environment: Java 6, MacOSX 10.6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>             Fix For: 0.5.0
>
>
> When select a column family, the only way to figure out all columns inside the column
family is to do a scan.  Since HBase does not have an API to get column names only, we have
to provide a temporary workaround.  We can add an option to do full table scan, and we scan
small amount of data to figure out the column patterns by default.  This short cut make assumption
that data are in repeated pattern, scanning one row should be sufficient to find all the columns.
 The same principle applies in scanning for unique row names.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message