[
https://issues.apache.org/jira/browse/CRUNCH-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominique Dierickx updated CRUNCH-330:
--------------------------------------
Attachment: 0001-working-version.patch
I made a first attempt at implementing this feature. A user can disable
counters by setting "crunch.disable.output.counters" to true.
I chose to implement this with a null object to speed things up and avoid a
conditional. I also added integration test for a run with and without counters
as well.
Let me know what you think,
Dominique
> Use of multiple output counters can be disabled in configuration.
> -----------------------------------------------------------------
>
> Key: CRUNCH-330
> URL: https://issues.apache.org/jira/browse/CRUNCH-330
> Project: Crunch
> Issue Type: New Feature
> Components: Core, IO
> Reporter: Dominique Dierickx
> Assignee: Josh Wills
> Priority: Minor
> Attachments: 0001-working-version.patch
>
>
> We're having some trouble with the amount of counters that Crunch creates
> when writing to a lot of different output files (slightly more than 120).
> This wouldn't be an issue if we were able to configure the maximum number
> of allowed counters but unfortunately, because we are running an older
> version of Hadoop, doing this is not an option and we are required to patch
> Crunch locally when using a new release to leave out the counters.
> I'm not saying the counters should be removed but maybe it is an option to
> make them configurable without paying too much of a performance penalty?
> I will implement this functionality and submit a patch.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
