[
https://issues.apache.org/jira/browse/ACCUMULO-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181395#comment-13181395
]
John Vines commented on ACCUMULO-255:
-------------------------------------
So that works great for ClassNotFoundException, but there are other cases, like
if a user has an NPE in their code.
> 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
