[
https://issues.apache.org/jira/browse/HBASE-8361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168991#comment-14168991
]
Hudson commented on HBASE-8361:
-------------------------------
SUCCESS: Integrated in HBase-TRUNK #5653 (See
[https://builds.apache.org/job/HBase-TRUNK/5653/])
HBASE-8361 Bulk load and other utilities should not create tables for user
(Ashish Singhi) (stack: rev 8e9a8b002ff088b9ea05aa6188d3c2bedec79a5a)
*
hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportTsv.java
*
hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFiles.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/ImportTsv.java
> 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
> Fix For: 2.0.0, 0.98.8, 0.99.2
>
> Attachments: HBASE-8361.patch
>
>
> {{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)
