[
https://issues.apache.org/jira/browse/ATLAS-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925647#comment-15925647
]
Madhan Neethiraj commented on ATLAS-1661:
-----------------------------------------
[~ssainath] - import-hive is generally meant for one-time use, to update Atlas
with the information from Hive metastore. It is not expected to be run
multiple-times; even if it is run multiple times, the tool wouldn't be able to
handle renames - as these information might not be available in Hive metastore.
> import hive script to handle updates like rename/delete
> -------------------------------------------------------
>
> Key: ATLAS-1661
> URL: https://issues.apache.org/jira/browse/ATLAS-1661
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-intg
> Reporter: Sharmadha Sainath
> Priority: Minor
>
> 1. Disabled hive hook
> 2. Created table table1
> 3. Ran import-hive.sh script , Atlas ingested table1.
> 4. Altered table table1 , rename to table1_new.
> 5. Ran import-hive.sh script , Atlas created a new table table1new .
> table1 wasn't updated with new name.
> This is the expected behavior with import-hive script as opposed to hive
> hook, as hive hook is synchronous and import-hive is not.
> But as a customer , running import-hive.sh multiple times and doing many hive
> operations may result in inconsistency while applying ranger policies to the
> table and in many scenarios , since it is not documented to run import hive
> script only once.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
