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 D621A1104E for ; Thu, 24 Jul 2014 20:02:38 +0000 (UTC) Received: (qmail 77917 invoked by uid 500); 24 Jul 2014 20:02:38 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 77869 invoked by uid 500); 24 Jul 2014 20:02:38 -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 77855 invoked by uid 99); 24 Jul 2014 20:02:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jul 2014 20:02:38 +0000 Date: Thu, 24 Jul 2014 20:02:38 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (ACCUMULO-3015) RangeInputSplit doesn't serialize table name MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Josh Elser created ACCUMULO-3015: ------------------------------------ Summary: RangeInputSplit doesn't serialize table name Key: ACCUMULO-3015 URL: https://issues.apache.org/jira/browse/ACCUMULO-3015 Project: Accumulo Issue Type: Bug Components: client Affects Versions: 1.6.0, 1.5.1 Reporter: Josh Elser Assignee: Josh Elser Fix For: 1.5.2, 1.6.1, 1.7.0 Found another missed member in the serialization of RangeInputSplit: the table name. Not a huge deal because the table information should still be in the Configuration for most users, but this does break in "advanced" uses of mapreduce. Work around is to re-set the table in the RangeInputSplit in your overridden InputFormat.getRecordReader or make sure the Configuration is consistent from getRecordReader and getSplits. -- This message was sent by Atlassian JIRA (v6.2#6252)