[
https://issues.apache.org/jira/browse/HBASE-10536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901709#comment-13901709
]
Nick Dimiduk commented on HBASE-10536:
--------------------------------------
bq. Maybe someone will want to load all what can be loaded, and deal with the
errors afterward.
Isn't bulkloading generally considered an "atomic" operation? I think allowing
a partial load is not ideal default behavior. If you want to allow partial
load, I'd prefer a "--no-strict" flag instead.
> ImportTsv should fail fast if any of the column family passed to the job is
> not present in the table
> ----------------------------------------------------------------------------------------------------
>
> Key: HBASE-10536
> URL: https://issues.apache.org/jira/browse/HBASE-10536
> Project: HBase
> Issue Type: Bug
> Components: mapreduce
> Affects Versions: 0.98.0
> Reporter: rajeshbabu
> Assignee: rajeshbabu
> Fix For: 0.96.2, 0.98.1, 0.99.0, 0.94.17
>
>
> While checking 0.98 rc, running bulkload tools. By mistake passed wrong
> column family to importtsv. LoadIncrementalHfiles failed with following
> exception
> {code}
> Exception in thread "main" java.io.IOException: Unmatched family names found:
> unmatched family names in HFiles to be bulkloaded: [f1]; valid family names
> of table test are: [f]
> at
> org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.doBulkLoad(LoadIncrementalHFiles.java:241)
> at
> org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.run(LoadIncrementalHFiles.java:823)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.main(LoadIncrementalHFiles.java:828)
> {code}
>
> Its better to fail fast if any of the passed column family is not present in
> table.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
