You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ashish Singhi (JIRA)" <ji...@apache.org> on 2014/10/09 13:10:34 UTC
[jira] [Commented] (HBASE-8361) Bulk load and other utilities
should not create tables for user
[ https://issues.apache.org/jira/browse/HBASE-8361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164997#comment-14164997 ]
Ashish Singhi commented on HBASE-8361:
--------------------------------------
As [~apurtell] suggests. We can add -Dcreate.table=yes/no argument to the tool, default set to yes to avoid backward incompatibility. Based on this we can decide whether to create a table or not.
I will prepare a patch for this if no objection.
> Bulk load and other utilities should not create tables for user
> ---------------------------------------------------------------
>
> Key: HBASE-8361
> URL: https://issues.apache.org/jira/browse/HBASE-8361
> Project: HBase
> Issue Type: Improvement
> Components: mapreduce
> Reporter: Nick Dimiduk
> Assignee: Ashish Singhi
>
> {{LoadIncrementalHFiles}} and {{ImportTsv}} will create a table with the default setting when the target table does not exist. I think this is an anti-feature. Neither tool provide a mechanism for the user to configure the creation parameters of that table, resulting in a new table with the default settings. I think it is unlikely that the default settings are what the user actually wants. In the event of a table-name typo, that means data is silently loaded into the wrong place. The tools should error when the destination table does not exist.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)