accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3094) Pass back stack traces when server side exception occurs
Date Fri, 29 Aug 2014 18:13:53 GMT

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

Keith Turner commented on ACCUMULO-3094:
----------------------------------------

bq. Do we want to be leaking server-state back to clients, though

I can not think of a reason not at the moment.  But I think there probably is a plausible
situation where you would not want to expose the information.  Maybe the best course of action
is to make it configurable, and have the default config preserve current behaviour.  But also
allow configuration for sending back more information. 

> 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.2#6252)

Mime
View raw message