Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Fri, 18 Apr 2014 21:28:16 +0000 (UTC)
From: "Sean Busbey (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12709344.1397854229487.141511.1397856496338@arcas>
In-Reply-To: <JIRA.12709344.1397854229487@arcas>
References: <JIRA.12709344.1397854229487@arcas>
Subject: [jira] [Updated] (ACCUMULO-2699) Conditional writer lacks trace
 level logging
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sean Busbey updated ACCUMULO-2699:
----------------------------------

    Affects Version/s: 1.6.0
        Fix Version/s: 1.6.1

> Conditional writer lacks trace level logging
> --------------------------------------------
>
>                 Key: ACCUMULO-2699
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2699
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.6.0
>            Reporter: Keith Turner
>             Fix For: 1.6.1, 1.7.0
>
>
> The conditional writer code lacks trace logging about what its doing.  Other client code like BatchWriter, BatchScanner, and Scanner have this.  
> It should like events like :
>  * sending X to tserver Y
>  * requeued X failed mutations
> These are not per mutations, but identify what its doing w/ batches of mutations.
> Noticed this while debugging ACCUMULO-2695


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