Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Sat, 10 May 2014 22:13:05 +0000 (UTC)
From: "Keith Turner (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12537390.1325791571228.322454.1399759985466@arcas>
In-Reply-To: <JIRA.12537390.1325791571228@arcas>
References: <JIRA.12537390.1325791571228@arcas>
Subject: [jira] [Updated] (ACCUMULO-255) Improve Iterator Debugging
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Keith Turner updated ACCUMULO-255:
----------------------------------

    Assignee:     (was: Keith Turner)

> Improve Iterator Debugging
> --------------------------
>
>                 Key: ACCUMULO-255
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-255
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: tserver
>            Reporter: John Vines
>
> There is currently little to no information provided to end users when there is a failure in custom iterators. We do not want to provide the full stack trace for security purposes, but that doesn't mean we can't provide some error information like error name (particularly ClassNotFoundException) or any exception which stems directly from the written iterator. Or we could have it return the partial stack trace from just within the iterator itself.


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