accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-2272) Refactor metadata operations into a common API
Date Sat, 04 Apr 2015 02:48:33 GMT

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

Josh Elser updated ACCUMULO-2272:
---------------------------------
    Fix Version/s:     (was: 1.7.0)
                   1.8.0

> Refactor metadata operations into a common API
> ----------------------------------------------
>
>                 Key: ACCUMULO-2272
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2272
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Christopher Tubbs
>             Fix For: 1.8.0
>
>
> We have a lot of code that updates/modifies entries in the metadata tables, and provides
metadata information for tablets to clients. It'd be better (code readability, modifiability)
if we could abstract these metadata operations into a usable API, rather than have separate
code spread out for the different kinds of metadata (zookeeper for the root table, root table
for the metadata tablets, metadata table for user tablets).
> A single API, with a factory to get the right implementation, depending on which table's
metadata is being manipulated, would be much easier to work with and would help avoid bugs
related to tablet management, updating table state, etc.
> A minimal API has been added (o.a.a.core.metadata.MetadataServicer) when the root tablet
was moved to its own table, as a starting point, but was not fully leveraged due to time constraints.
> To be clear, this improvement is entirely refactoring of internal code. User experience
should have no impact (unless it helps find/prevent bugs).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message