[
https://issues.apache.org/jira/browse/SQOOP-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16376467#comment-16376467
]
Hajime Osako commented on SQOOP-2936:
-------------------------------------
Correct me if I'm wrong but wouldn't this calls SqoopHook in
PublishJobData.publishJobData() *before* Loading uploaded data into Hive?
So that if the import job fails (eg: the target database didn't exist), Atlas
thinks the table has been imported but actually no table in hive metadata.
If my guess is correct, was this because of some technical
restriction/limitation?
> Provide Apache Atlas integration for hcatalog based exports
> -----------------------------------------------------------
>
> Key: SQOOP-2936
> URL: https://issues.apache.org/jira/browse/SQOOP-2936
> Project: Sqoop
> Issue Type: Bug
> Reporter: Balu Vellanki
> Assignee: Balu Vellanki
> Priority: Major
> Fix For: 1.4.7
>
> Attachments: SQOOP-2936-v1.patch, SQOOP-2936-v2.patch,
> SQOOP-2936-v3.patch, SQOOP-2936-v4.patch, SQOOP-2936.patch
>
>
> We would like to provide lineage information to Apache Atlas when data is
> exported from Hcatalog via Sqoop. This will allow us to identify the lineage
> of data.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
