You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "John Vines (Created) (JIRA)" <ji...@apache.org> on 2012/01/05 20:26:39 UTC
[jira] [Created] (ACCUMULO-255) Improve Iterator Debugging
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
[jira] [Commented] (ACCUMULO-255) Improve Iterator Debugging
Posted by "Eric Newton (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (ACCUMULO-255) Improve Iterator Debugging
Posted by "John Vines (Commented) (JIRA)" <ji...@apache.org>.
[ 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