accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-3238) Replace String tableName arguments with TableHandle
Date Thu, 16 Oct 2014 19:13:33 GMT

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

Eric Newton updated ACCUMULO-3238:
----------------------------------
    Issue Type: Sub-task  (was: Improvement)
        Parent: ACCUMULO-2589

> Replace String tableName arguments with TableHandle
> ---------------------------------------------------
>
>                 Key: ACCUMULO-3238
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3238
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client
>            Reporter: John Vines
>
> All of our client operations work by table name. This present awkward cases around renames.
A solution to this is making all operations work around table IDs, but this isn't user friendly.
A middle ground is introducing a TableHandle, which is a container for the user to use, with
the implication that if a rename happens, the operations will follow the table. This is similar
to how filesystems deal with renames.
> This way we have the translation between table name->id done VERY early on and done
explicitly to the users knowledge so they can make guarantees about operations.
> I would see there being an operation added for getTableHandle which takes the name and
then that handle is used for all future operations.
> By putting things in a TableHandle, we can have a minor first pass which ges the API
in place and then we can work on ensuring no name->id mapping occurs deeper in the server
to help make sure things are consistent.



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

Mime
View raw message