Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@crunch.apache.org
Date: Mon, 20 Oct 2014 02:41:34 +0000 (UTC)
From: "Micah Whitacre (JIRA)" <jira@apache.org>
To: crunch-dev@incubator.apache.org
Message-ID: <JIRA.12749127.1413756497000.294239.1413772894516@Atlassian.JIRA>
In-Reply-To: <JIRA.12749127.1413756497000@Atlassian.JIRA>
References: <JIRA.12749127.1413756497000@Atlassian.JIRA>
 <JIRA.12749127.1413756497895@arcas>
Subject: [jira] [Assigned] (CRUNCH-476) Logging API Consistency
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Micah Whitacre reassigned CRUNCH-476:
-------------------------------------

    Assignee: Micah Whitacre  (was: Josh Wills)

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