[
https://issues.apache.org/jira/browse/HBASE-8361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166476#comment-14166476
]
Hadoop QA commented on HBASE-8361:
----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12674109/HBASE-8361.patch
against trunk revision .
ATTACHMENT ID: 12674109
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 8 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11299//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11299//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11299//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11299//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11299//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11299//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11299//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11299//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11299//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11299//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11299//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11299//console
This message is automatically generated.
> 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
> 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)
