[
https://issues.apache.org/jira/browse/SQOOP-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16559467#comment-16559467
]
Hudson commented on SQOOP-3353:
-------------------------------
SUCCESS: Integrated in Jenkins build Sqoop-hadoop200 #1190 (See
[https://builds.apache.org/job/Sqoop-hadoop200/1190/])
SQOOP-3353: Sqoop should not check incremental constraints for HBase (bogi:
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=a06f2f3a8305b7a58b35e27f1fa6aea820dda5aa])
* (edit) src/test/org/apache/sqoop/tool/TestImportTool.java
* (edit) src/java/org/apache/sqoop/tool/ImportTool.java
* (edit) src/test/org/apache/sqoop/TestIncrementalImport.java
> Sqoop should not check incremental constraints for HBase imports
> ----------------------------------------------------------------
>
> Key: SQOOP-3353
> URL: https://issues.apache.org/jira/browse/SQOOP-3353
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.4.7
> Reporter: Szabolcs Vasas
> Assignee: Szabolcs Vasas
> Priority: Major
> Attachments: SQOOP-3353.patch
>
>
> ImportTool#initIncrementalConstraints method is invoked for every import in
> Sqoop and it can throw the following error even for HBase imports:
> {code:java}
> --merge-key or --append is required when using --incremental lastmodified and
> the output directory exists.{code}
> The task is to fix the validation not to throw an exception when importing
> into an HBase table since in that case it does not matter if the table
> directory exists on HDFS.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
