Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 21 Apr 2015 22:29:59 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12787276.1427873229000.67898.1429655399352@Atlassian.JIRA>
In-Reply-To: <JIRA.12787276.1427873229000@Atlassian.JIRA>
References: <JIRA.12787276.1427873229000@Atlassian.JIRA>
 <JIRA.12787276.1427873229515@arcas>
Subject: [jira] [Commented] (CASSANDRA-9084) Do not generate line number in
 logs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brandon Williams commented on CASSANDRA-9084:
---------------------------------------------

The simplest thing to do here is revert, unless someone can provide empirical evidence that this optimization is worthwhile.  And as Jeremiah mentioned, the user can always remove the line numbers themselves.

> Do not generate line number in logs
> -----------------------------------
>
>                 Key: CASSANDRA-9084
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9084
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Config
>            Reporter: Andrey
>            Assignee: Benedict
>            Priority: Minor
>
> According to logback documentation (http://logback.qos.ch/manual/layouts.html):
> {code}
> Generating the line number information is not particularly fast. Thus, its use should be avoided unless execution speed is not an issue.
> {code}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)