crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Micah Whitacre (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CRUNCH-476) Logging API Consistency
Date Mon, 20 Oct 2014 02:41:35 GMT

    [ https://issues.apache.org/jira/browse/CRUNCH-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176546#comment-14176546
] 

Micah Whitacre commented on CRUNCH-476:
---------------------------------------

Generally yeah, but if we landed on one like log4j or commons-logging slf4j would let someone
swap out the impl.  I'll take a stab at cleaning this up will involve some dependency changes.

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

Mime
View raw message