Mailing-List: contact dev-help@falcon.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.incubator.apache.org
Date: Thu, 24 Apr 2014 14:00:48 +0000 (UTC)
From: "Shwetha G S (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12670425.1380092147559.172435.1398348048462@arcas>
In-Reply-To: <JIRA.12670425.1380092147559@arcas>
References: <JIRA.12670425.1380092147559@arcas>
Subject: [jira] [Commented] (FALCON-133) Upgrade to slf4j 1.7.5 and use
 SLF4J logger
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/FALCON-133?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1397=
9748#comment-13979748 ]=20

Shwetha G S commented on FALCON-133:
------------------------------------

{quote}
 Would this create a runtime conflict (haven't checked myself to see if 1.7=
.5 is fully backward compatible with 1.4.3 & later) ? Can you please confir=
m if this doesn't break anything particularly retention, replication, recor=
dsize and post-processing actions? If there are no conflicts, this would be=
 a good change.
{quote}
Can you also check this?

> Upgrade to slf4j 1.7.5 and use SLF4J logger
> -------------------------------------------
>
>                 Key: FALCON-133
>                 URL: https://issues.apache.org/jira/browse/FALCON-133
>             Project: Falcon
>          Issue Type: Improvement
>          Components: general
>            Reporter: Jean-Baptiste Onofr=C3=A9
>            Assignee: Jean-Baptiste Onofr=C3=A9
>         Attachments: FALCON-133.patch
>
>
> SLF4J 1.7.5 provides interesting performance improvements.
> More over, it's not more require to test the log level, we can use direct=
ly {} in the message formatter.


--
This message was sent by Atlassian JIRA
(v6.2#6252)