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 71BC110E22 for ; Wed, 16 Oct 2013 02:49:51 +0000 (UTC) Received: (qmail 32109 invoked by uid 500); 16 Oct 2013 02:49:45 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 31978 invoked by uid 500); 16 Oct 2013 02:49:44 -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 31843 invoked by uid 99); 16 Oct 2013 02:49:44 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Oct 2013 02:49:44 +0000 Date: Wed, 16 Oct 2013 02:49:43 +0000 (UTC) From: "Corey J. Nolet (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (ACCUMULO-1732) Resolve table name to table id once in Accumulo input format 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-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Corey J. Nolet resolved ACCUMULO-1732. -------------------------------------- Resolution: Fixed Fix Version/s: 1.6.0 > Resolve table name to table id once in Accumulo input format > ------------------------------------------------------------ > > Key: ACCUMULO-1732 > URL: https://issues.apache.org/jira/browse/ACCUMULO-1732 > Project: Accumulo > Issue Type: Bug > Affects Versions: 1.4.0 > Reporter: Keith Turner > Assignee: Corey J. Nolet > Priority: Minor > Fix For: 1.6.0 > > > AccumuloInputFormat (and I suspect AccumuloOutputFormat) sends the table name to each mapper. The mapper uses this table name to create a scanner. In the case of the following events a map reduce job could read from two different table ids. > # start M/R job reading table A > # rename table A (tableId=1) to table C > # rename table B (tableId=2) to table A > If the input format passed table id 1 to the mappers, then the renames would not cause a problem. -- This message was sent by Atlassian JIRA (v6.1#6144)