[
https://issues.apache.org/jira/browse/HBASE-9895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey Zhong updated HBASE-9895:
---------------------------------
Release Note:
To import 0.94 exported file in 0.96 cluster or onwards, you need to set system
property "hbase.import.version" when running the import command as below:
./bin/hbase -Dhbase.import.version=0.94
org.apache.hadoop.hbase.mapreduce.Import <table name> <import file folder>
was:
To import 0.94 exported file in 0.96 cluster or onwards, you need to set system
property "hbase.import.version" when running the import command as below:
{code}
./bin/hbase -Dhbase.import.version=0.94
org.apache.hadoop.hbase.mapreduce.Import <table name> <import file folder>
{code}
> 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: 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#6144)
