[
https://issues.apache.org/jira/browse/ACCUMULO-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Miller reassigned ACCUMULO-3238:
----------------------------------------
Assignee: Michael Miller (was: Christopher Tubbs)
> 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
> Assignee: Michael Miller
> Fix For: 2.0.0
>
>
> 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.15#6346)
