accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-1966) Clone table has race condition when excluding namespace properties
Date Mon, 30 Dec 2013 18:07:51 GMT

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

Christopher Tubbs resolved ACCUMULO-1966.
-----------------------------------------

    Resolution: Fixed
      Assignee: Christopher Tubbs

I believe I fixed this with a commit against ACCUMULO-1965. The relevant client-side code
was removed, and relies on the server-side copy of the source table's config.

> Clone table has race condition when excluding namespace properties
> ------------------------------------------------------------------
>
>                 Key: ACCUMULO-1966
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1966
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client, master, tserver
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>             Fix For: 1.6.0
>
>
> Found on ReviewBoard for ACCUMULO-802:
> The clone method excludes  properties which are unique to namespaces with a getUniqueNamespaceProperties()
method.
> # I'm not sure it should be doing this at all (should a clone have the same behavior,
plus any additional configuration not overridden by the table, when it appears in the new
namespace, or should it only clone the properties that distinguish it from the namespace it
was previously in?)
> # It could suffer from race conditions, because it is checking on the client side.
> (Creating this ticket, so I can close the ReviewBoard one).



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message