[jira] [Resolved] (ACCUMULO-3855) ProxyServer.update fails silently if batchwriter doesn't exist

["Christopher Tubbs (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ACCUMULO-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher Tubbs resolved ACCUMULO-3855.
-----------------------------------------
       Resolution: Won't Fix
    Fix Version/s:     (was: 1.7.1)
                       (was: 1.8.0)
                       (was: 1.6.3)
                       (was: 1.5.3)

Since this isn't really possible to address with the current design, I'm going to go ahead and close this as "Won't Fix", after discussing briefly with [~elserj] in IRC. It's a known potential problem, but not much we can do about it at this point. If somebody has an idea, we can revisit it later.

> ProxyServer.update fails silently if batchwriter doesn't exist
> --------------------------------------------------------------
>
>                 Key: ACCUMULO-3855
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3855
>             Project: Accumulo
>          Issue Type: Bug
>          Components: proxy
>            Reporter: Josh Elser
>            Priority: Critical
>
> Inspecting ProxyServer, saw the following:
> {code}
>   @Override
>   public void update(String writer, Map<ByteBuffer,List<ColumnUpdate>> cells) throws TException {
>     try {
>       BatchWriterPlusException bwpe = getWriter(writer);
>       addCellsToWriter(cells, bwpe);
>     } catch (UnknownWriter e) {
>       // just drop it, this is a oneway thrift call and throwing a TException seems to make all subsequent thrift calls fail
>     }
>   }
> {code}
> This means that calls to update which fail to get a BatchWriter (for whatever reason) will silently fail and appear to the user to have written data successfully. This is horrible.
> I'm not sure what the comment means either. I'm not sure why throwing a TException from the server would invalidate the connection, but perhaps I'm just ignorant of some finer details.



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