[
https://issues.apache.org/jira/browse/ACCUMULO-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292403#comment-14292403
]
Josh Elser commented on ACCUMULO-3530:
--------------------------------------
Makes sense: the state/config of the source table when the cloneTable() is
started should be the same as the config on the resulting cloned table, right?
> alterTable/NamespaceProperty should use Fate locks
> --------------------------------------------------
>
> Key: ACCUMULO-3530
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3530
> Project: Accumulo
> Issue Type: Bug
> Reporter: John Vines
>
> Fate operations, such as clone table, have logic in place to ensure
> consistency as the operation occurs. However, operaitons like
> alterTableProperty can still interfere because there is no locking done. We
> should add identical locking to these methods in MasterClientServiceHandler
> to help ensure consistency.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
