accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3094) Pass back stack traces when server side exception occurs
Date Wed, 03 Sep 2014 01:55:52 GMT

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

Christopher Tubbs commented on ACCUMULO-3094:
---------------------------------------------

Yeah, I like the idea of a development mode, like is common for web servers / frameworks,
as [~elserj] points out, but the default should be off, like [~kturner] said. This should
be a server-side configuration (general.server.stacktrace.verbosity=(none, partial, full)?).
Clients shouldn't be able to choose how much detail is returned. It should be a mode that
an admin chooses, either with a restart, or (maybe) a live configuration change.

> Pass back stack traces when server side exception occurs 
> ---------------------------------------------------------
>
>                 Key: ACCUMULO-3094
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3094
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Keith Turner
>             Fix For: 1.7.0
>
>
> Was discussing ACCUMULO-3092 w/ [~dlmarion] and the issue of why more info about server
side exceptions was not transmitted back to client came up.  This was a concious design decision
made in Accumulo to avoid unintentionally leaking information to the client.   The main concern
is the exception message on the server side, that message could have been constructed w/ data
from Accumulo.
> We discussed the possibility of dropping the exception message[s] and sending the stack
trace[s] back to the client side.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message