Umesh Padashetty created ATLAS-4334:
---------------------------------------
Summary: Creating an external table/database, overrides the
qualfiedName of an already existing aws_s3_v2_directory type
Key: ATLAS-4334
URL: https://issues.apache.org/jira/browse/ATLAS-4334
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Umesh Padashetty
The expectation is that every time an EXTERNAL Table is created in Hive, Atlas
creates an entity of type hive_process connecting the aws_s3_v2_directory and
the hive_table
A new unique entity of the type aws_s3_v2_directory and hive_table is created
in atlas for every new external table created.
For instance, if I create an external table with the name test_ext_1, then
there is an aws_s3_v2_directory and hive_table entity created with a similar
name test_ext_1
But observing a strange behaviour where whenever a new external table is
created, even though a new hive_table entity is created, the previously created
aws_s3_v2_directory entity itself is getting overridden with the new
qualifiedName
For instance, I ran the below queries
* create external table test_ext_1(name string);
* create external table test_ext_2(name string);
* create external table test_ext_3(name string);
* create database net1;
The expectation is that the above 4 queries will create
* 3 hive_table entities
* 1 hive_db entity
* 3 aws_s3_v2_directory entities
But it is actually creating
* 3 hive_table entities
* 1 hive_db entity
* 1 aws_s3_v2_directory entity
The same aws_s3_v2_directory gets updated with a new qualifiedName every time I
create a new external table or a database
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
