Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2FDCA17738 for ; Thu, 16 Oct 2014 19:13:34 +0000 (UTC) Received: (qmail 7993 invoked by uid 500); 16 Oct 2014 19:13:34 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 7962 invoked by uid 500); 16 Oct 2014 19:13:34 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 7951 invoked by uid 99); 16 Oct 2014 19:13:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Oct 2014 19:13:33 +0000 Date: Thu, 16 Oct 2014 19:13:33 +0000 (UTC) From: "Eric Newton (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-3238) Replace String tableName arguments with TableHandle MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)