Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 8 Nov 2013 19:28:19 +0000 (UTC)
From: "Nick Dimiduk (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12677625.1383678365397.43750.1383938899257@arcas>
In-Reply-To: <JIRA.12677625.1383678365397@arcas>
References: <JIRA.12677625.1383678365397@arcas>
Subject: [jira] [Commented] (HBASE-9895) 0.96 Import utility can't import an
 exported file from 0.94
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-9895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817601#comment-13817601 ] 

Nick Dimiduk commented on HBASE-9895:
-------------------------------------

Alright then. Any chance of adding some kind of test? Maybe a data blob that matches the old format? Looks good otherwise.

> 0.96 Import utility can't import an exported file from 0.94
> -----------------------------------------------------------
>
>                 Key: HBASE-9895
>                 URL: https://issues.apache.org/jira/browse/HBASE-9895
>             Project: HBase
>          Issue Type: Bug
>          Components: mapreduce
>    Affects Versions: 0.96.0
>            Reporter: Jeffrey Zhong
>            Assignee: Jeffrey Zhong
>         Attachments: hbase-9895.patch
>
>
> Basically we PBed org.apache.hadoop.hbase.client.Result so a 0.96 cluster cannot import 0.94 exported files. This issue is annoying because a user can't import his old archive files after upgrade or archives from others who are using 0.94.
> The ideal way is to catch deserialization error and then fall back to 0.94 format for importing.


--
This message was sent by Atlassian JIRA
(v6.1#6144)