chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Yang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CHUKWA-564) HBase output collector uses incorrect column family
Date Sat, 11 Dec 2010 01:57:00 GMT

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

Eric Yang commented on CHUKWA-564:
----------------------------------

Chukwa use case:

SystemMetrics adaptor is emitting SystemMetrics data type.  SystemMetrics data processor is
writing data to SystemMetrics table, column family: cpu, disk, memory.

This is currently possible by using reducer type as grouping for cpu, disk memory.

I disagree on data routing decouple from the processor for two reason. 

1. Indirection mapping configuration is difficult to maintain on distributed system.
2. Add extra overhead to the processor for lookup data routing.

The use case is not writing the same data to different column family, but split subtype data
into different column family.

> HBase output collector uses incorrect column family
> ---------------------------------------------------
>
>                 Key: CHUKWA-564
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-564
>             Project: Chukwa
>          Issue Type: Bug
>            Reporter: Bill Graham
>             Fix For: 0.5.0
>
>
> The HBase {{OutputCollector}} does this to obtain the column family from the data type:
> {noformat}
> cf = key.getReduceType().getBytes();
> {noformat}
> The column family should instead be taken by the {{@Table.columnFamily}} annotation on
the processor.

-- 
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