You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@accumulo.apache.org by "Eric Newton (Commented) (JIRA)" <ji...@apache.org> on 2012/01/06 00:19:39 UTC

[jira] [Commented] (ACCUMULO-255) Improve Iterator Debugging

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

Eric Newton commented on ACCUMULO-255:
--------------------------------------

The client code (the shell, the AccumuloInputFormat) do a check that an arbitrary tablet server can load a class that provides a given interface.  This creates an early fail-fast for most casual users of extensions.  Update this ticket for particular use-cases where the check is missing.

                
> 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
>            Assignee: Keith Turner
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira