[
https://issues.apache.org/jira/browse/ACCUMULO-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292212#comment-14292212
]
John Vines commented on ACCUMULO-3530:
--------------------------------------
When I issue a clone table command, for instance, I expect the copied table's
iterator settings to match the settings the source table had when I issue a
command. Currently we cannot make that guarantee.
> 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)
