[jira] [Comment Edited] (HBASE-9895) 0.96 Import utility can't import an exported file from 0.94

["Jonathan Hsieh (JIRA)" <ji...@apache.org>]

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

Jonathan Hsieh edited comment on HBASE-9895 at 12/17/13 4:29 PM:
-----------------------------------------------------------------

[~jeffreyz] This option should be documented in the usage (run with no args) and in the refguide here http://hbase.apache.org/book.html#import .  Mind doing a follow on and adding documentation (cut and past of new usage would be great)?  See importTsv for a similar example.


was (Author: jmhsieh):
[~jeffreyz] This option should be documented in the usage (run with no args) and in the refguide here http://hbase.apache.org/book.html#import .  Mind doing a follow on and adding documentation (cut and past of new usage would be great).  See importTsv for a similar example.

> 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
>             Fix For: 0.98.0, 0.96.1
>
>         Attachments: exportedTableIn94Format, hbase-9895-v2.patch, hbase-9895-v3.patch, 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.4#6159)