[
https://issues.apache.org/jira/browse/ACCUMULO-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13596364#comment-13596364
]
Keith Turner commented on ACCUMULO-1163:
----------------------------------------
Maybe throwing table deleted exception is not the right thing to do. I just
noticed that setProperty() is not handling deleted tables well when looking at
the following code in test.randomwalk.concurrent.Config.
{code:java}
try {
state.getConnector().tableOperations().setProperty(table,
property.getKey(), property.getDefaultValue());
} catch (AccumuloException ex) {
if (ex.toString().contains("NoNode for")) {
// race condition for a table that has been deleted
} else {
throw ex;
}
}
{code}
{code:java}
try {
state.getConnector().tableOperations().setProperty(table,
setting.property.getKey(), "" + newValue);
} catch (AccumuloException ex) {
if (ex.getCause() instanceof ThriftTableOperationException) {
ThriftTableOperationException ttoe =
(ThriftTableOperationException)ex.getCause();
if (ttoe.type == TableOperationExceptionType.NOTFOUND)
return;
}
throw ex;
}
{code}
> Throw TableDeletedException
> ---------------------------
>
> Key: ACCUMULO-1163
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1163
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Reporter: Keith Turner
> Assignee: Billie Rinaldi
> Fix For: 1.6.0
>
>
> ACCUMULO-1115 highlights that TableOperations.setProperty is not throwing a
> TableDeleted exception. It probably should throw this exception. Need to
> determine what other methods should throw this exception.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
