[
https://issues.apache.org/jira/browse/CRUNCH-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Micah Whitacre updated CRUNCH-476:
----------------------------------
Attachment: CRUNCH-476_v2.patch
We need to probably log more because uplifting the log messages wasn't too
difficult. Also removed the commons-logging dependency from the room POM.
Also was curious if someone would notice that (didn't help unfortunately). I
remove for official commit.
> Logging API Consistency
> -----------------------
>
> Key: CRUNCH-476
> URL: https://issues.apache.org/jira/browse/CRUNCH-476
> Project: Crunch
> Issue Type: Improvement
> Components: Core
> Reporter: Micah Whitacre
> Assignee: Micah Whitacre
> Attachments: CRUNCH-476.patch, CRUNCH-476_v2.patch
>
>
> Poking around the code I noticed that HBase uses log4j while most of
> crunch-core, crunch-spark use commons-logging. If the variation is justified
> that is fine but for consumer wanting to consistently configure logging for
> Crunch jobs it would be nice to use a consistent API and then let them
> configure it one way.
> Our options are possibly to converge on one implementation or move to
> something like slf4j and allow consumers to swap out the impl at assembly
> time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
