You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Dharshana M Krishnamoorthy (Jira)" <ji...@apache.org> on 2022/04/28 07:28:00 UTC
[jira] [Updated] (ATLAS-4595) [Hive import v2] When using file name to import via v2 api, the tables of the imported db are not reflected
[ https://issues.apache.org/jira/browse/ATLAS-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dharshana M Krishnamoorthy updated ATLAS-4595:
----------------------------------------------
Summary: [Hive import v2] When using file name to import via v2 api, the tables of the imported db are not reflected (was: [Hive import v2] When using file name to import via v2 api, the tables of the imported )
> [Hive import v2] When using file name to import via v2 api, the tables of the imported db are not reflected
> -----------------------------------------------------------------------------------------------------------
>
> Key: ATLAS-4595
> URL: https://issues.apache.org/jira/browse/ATLAS-4595
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Reporter: Dharshana M Krishnamoorthy
> Priority: Major
>
> Scenario:
> use --filename in the import script in along with --output so that v2 api is invoked
> Eg:
> {code:java}
> '/opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-hive.sh --filename /tmp/file_hqavs.txt --output /tmp/db_axmqv.zip {code}
> There is some delay (few seconds) before it reflects in atlas.
> Steps:
> # Create 2 databases db_1 and db_2
> # Run import using filename that has tables belonging to database1
> When a search is performed immediately after the import, the data is not reflected in atlas, if we wait for 5 seconds and then search again, data is reflected.
> This does not happen in the following scenarios:
> # when v1 api is used
> # when v2 api is used with database name
> # when v2 api is used with table name
> *It happens only when v2 api is used along with file name*
> This is not a blocker bug as the data reflects in atlas.
> But creating to find the reason why this happens only while using file name in v2 api.
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)