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] [Resolved] (CRUNCH-476) Logging API Consistency
Date Tue, 28 Oct 2014 01:12:33 GMT

     [ https://issues.apache.org/jira/browse/CRUNCH-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Micah Whitacre resolved CRUNCH-476.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 0.12.0

Changes have been pushed to master.

> 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
>             Fix For: 0.12.0
>
>         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)

Mime
View raw message