chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Graham (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CHUKWA-473) Make default processor configurable
Date Tue, 06 Apr 2010 22:49:33 GMT

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

Bill Graham commented on CHUKWA-473:
------------------------------------

OK cool, we're talking about the same functionality. Regarding the naming then, what was causing
me confusion that your config name ends with 'defaultMapper'. It makes it look like the config
takes a Mapper class. I think it would be more clear if we used language that refers to Processors
or MapProcessors, not Mappers. This is because the thing that we're configuring is actually
an instance of {{org.apache.hadoop.chukwa.extraction.demux.processor.mapper.MapProcessor}},
not {Mapper}. 

What about {{chukwa.demux.mapper.default.processor}}?

> Make default processor configurable
> -----------------------------------
>
>                 Key: CHUKWA-473
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-473
>             Project: Hadoop Chukwa
>          Issue Type: New Feature
>            Reporter: Bill Graham
>            Assignee: Bill Graham
>
> The default processor is hard coded to {{DefaultProcessor}} in the {{Demux}} class. This
should be configurable.

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