You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2023/05/21 12:28:00 UTC
[jira] [Resolved] (HBASE-27848) Should fast-fail if unmatched column family exists when using ImportTsv
[ https://issues.apache.org/jira/browse/HBASE-27848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Duo Zhang resolved HBASE-27848.
-------------------------------
Fix Version/s: 2.6.0
3.0.0-alpha-4
2.5.5
2.4.18
Resolution: Fixed
> Should fast-fail if unmatched column family exists when using ImportTsv
> -----------------------------------------------------------------------
>
> Key: HBASE-27848
> URL: https://issues.apache.org/jira/browse/HBASE-27848
> Project: HBase
> Issue Type: Improvement
> Components: mapreduce
> Affects Versions: 2.4.13
> Environment: Centos 7
> HBase 2.4.13
> Reporter: guluo
> Assignee: guluo
> Priority: Major
> Fix For: 2.6.0, 3.0.0-alpha-4, 2.5.5, 2.4.18
>
>
> Executing cmd as following:
> {code:java}
> //code
> hbase org.apache.hadoop.hbase.mapreduce.ImportTsv -Dimporttsv.separator=, -Dimporttsv.columns=HBASE_ROW_KEY,temp01_error01:first_name,temp01_error02:last_name test_hbase hdfs:///tmp/hbase_data.csv {code}
> If We specify a error column family(it does not exists), this operation would not fail until MR job is executed
> It is better to fast-fail before MR is submitted if we specify a error column family
--
This message was sent by Atlassian Jira
(v8.20.10#820010)