[
https://issues.apache.org/jira/browse/CHUKWA-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718639#action_12718639
]
Jiaqi Tan commented on CHUKWA-282:
----------------------------------
I think a simple unit test would be reasonable in this case, just to sanity
check the code. It's essentially just moving all the key/value pairs in each
cilenttrace message into the final post-Demux output. The unit test should be
pretty trivial but would make sense in any case.
> Demux should output detailed per-operation ClientTrace records
> --------------------------------------------------------------
>
> Key: CHUKWA-282
> URL: https://issues.apache.org/jira/browse/CHUKWA-282
> Project: Hadoop Chukwa
> Issue Type: Improvement
> Components: Data Processors
> Affects Versions: 0.2.0
> Reporter: Jiaqi Tan
> Assignee: Jiaqi Tan
> Priority: Minor
> Fix For: 0.2.0
>
> Attachments: CHUKWA-282.patch
>
>
> Currently, the ClientTrace reducer in Demux summarizes client trace
> operations to produce aggregate statistics for each type of operation (e.g.
> total bytes of local HDFS reads, total bytes of local HDFS writes). However,
> more sophisticated algorithms and visualization will need more detailed
> information such as amount of reads/writes to/from every pair of hosts. The
> ClientTrace reducer should also output the unsummarized, raw ClientTrace data
> so they can be used for analysis/visualization.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
