[
https://issues.apache.org/jira/browse/ACCUMULO-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Meisler updated ACCUMULO-3354:
------------------------------------
Status: Patch Available (was: In Progress)
Created an additional constructor for a TableOfflineException that takes the
table name as a parameter. Changed TableOperationsImpl.doFateOperation to use
the new constructor.
TableOperationsImpl.doFateOperation is the only method that passed an
explicitly null tableId to the TableOfflineException constructor. It is now
fixed. There isn't an easy way to test this since MockAccumulo doesn't mock
offline tables.
> Calling deleteRows on an offline table doesn't include table name in error
> --------------------------------------------------------------------------
>
> Key: ACCUMULO-3354
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3354
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.6.1
> Reporter: Josh Elser
> Assignee: Jacob Meisler
> Labels: newbie, summit2015
> Fix For: 1.6.3, 1.8.0, 1.7.1
>
>
> The table name that I provided to deleteRows should be included in the
> exception message.
> {noformat}
> org.apache.accumulo.core.client.TableOfflineException: Table <unknown table>
> is offline
> at
> org.apache.accumulo.core.client.impl.TableOperationsImpl.doFateOperation(TableOperationsImpl.java:333)
> at
> org.apache.accumulo.core.client.impl.TableOperationsImpl.doFateOperation(TableOperationsImpl.java:295)
> at
> org.apache.accumulo.core.client.impl.TableOperationsImpl.doTableFateOperation(TableOperationsImpl.java:1595)
> at
> org.apache.accumulo.core.client.impl.TableOperationsImpl.deleteRows(TableOperationsImpl.java:557)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
