[
https://issues.apache.org/jira/browse/SQOOP-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658564#comment-15658564
]
Eric Lin commented on SQOOP-1214:
---------------------------------
Hi Sai,
Can you confirm that you are talking about Sqoop1, not Sqoop2? I see that
affects version is 1.4.3, but Components is set as sqoop2-client. So I just
want to make sure.
Looks like this has been filed for a while, I will test and see if this is
still the case in latest release and I am happy to see if there is an option
available for a patch.
Thanks
> Sqoop import - importing table into HBASE with overwrite
> --------------------------------------------------------
>
> Key: SQOOP-1214
> URL: https://issues.apache.org/jira/browse/SQOOP-1214
> Project: Sqoop
> Issue Type: Bug
> Components: sqoop2-client
> Affects Versions: 1.4.3
> Environment: Sqoop 1.4.3-cdh4.4.0
> Reporter: Hari
> Priority: Critical
> Labels: patch
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Sqoop is not supporting Importing a oracle table into HBASE with full table
> replace option, where as the similar option is available in Hive (like hive
> overwrite option in sqoop), is there a way we can achieve this behavior with
> out going for "disbale 'table', drop 'table' before every sqoop import for
> this table.
> I do recommend that instead of sqooping full table every time, we can go for
> last updated column wise sqooping, what is the case if we have any
> restriction like last updated column is not exists or index on that that
> field is not exists.
> I feel it is better to have an option with over write.
> Ref:
> http://stackoverflow.com/questions/19217696/sqoop-import-importing-table-into-hbase-with-overwrite
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)