[
https://issues.apache.org/jira/browse/ATLAS-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Padashetty updated ATLAS-4311:
------------------------------------
Description:
The api/atlas/v2/entity/businessmetadata/import returns the incorrect Line
Number
For instance, following is the data in template file
{code:java}
EntityType,EntityUniqueAttributeValue,BusinessAttributeName,BusinessAttributeValue,EntityUniqueAttributeName[optional]
hive_table,hive_table_kcsup@cm,BM3.BM3A1,stringval
hive_table,invalid_table@cm,BM3.BM3A1,stringval {code}
As seen above, on line #3, we have entity name as invalid_table@cm, this entity
is not existing in atlas.
But the businessmetadata/import API returns
{code:java}
{ "failedImportInfoList": [ { "parentObjectName": "", "childObjectName": "",
"importStatus": "FAILED", "remarks": "Line #2: no hive_table entity found with
qualifiedName=invalid_table@cm" } ] } {code}
As seen above, Line number should have been returned as 3, but it is returned
as 2.
This probably is happening because we intrinsically ignore the first line in
the template file
was:
The api/atlas/v2/entity/businessmetadata/import returns the incorrect Line
Number
For instance, following is the data in template file
{code:java}
EntityType,EntityUniqueAttributeValue,BusinessAttributeName,BusinessAttributeValue,EntityUniqueAttributeName[optional]
hive_table,hive_table_kcsup@cm,BM3.BM3A1,stringval
hive_table,invalid_table@cm,BM3.BM3A1,stringval {code}
As seen above, on line #3, we have entity name as invalid_table@cm, this entity
is not existing in atlas.
But the businessmetadata/import API returns
{code:java}
{ "failedImportInfoList": [ { "parentObjectName": "", "childObjectName": "",
"importStatus": "FAILED", "remarks": "Line #2: no hive_table entity found with
qualifiedName=invalid_table@cm" } ] } {code}
As seen above, Line number should have been returned as 3, but it is returned
as 2.
This probably is happening because we intrinsically ignore the first line in
the template file
> [Business Metadata Bulk Import] Wrong Line Number returned in
> failedImportInfoList
> -----------------------------------------------------------------------------------
>
> Key: ATLAS-4311
> URL: https://issues.apache.org/jira/browse/ATLAS-4311
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Reporter: Umesh Padashetty
> Priority: Minor
>
> The api/atlas/v2/entity/businessmetadata/import returns the incorrect Line
> Number
> For instance, following is the data in template file
> {code:java}
> EntityType,EntityUniqueAttributeValue,BusinessAttributeName,BusinessAttributeValue,EntityUniqueAttributeName[optional]
>
> hive_table,hive_table_kcsup@cm,BM3.BM3A1,stringval
> hive_table,invalid_table@cm,BM3.BM3A1,stringval {code}
> As seen above, on line #3, we have entity name as invalid_table@cm, this
> entity is not existing in atlas.
> But the businessmetadata/import API returns
> {code:java}
> { "failedImportInfoList": [ { "parentObjectName": "", "childObjectName": "",
> "importStatus": "FAILED", "remarks": "Line #2: no hive_table entity found
> with qualifiedName=invalid_table@cm" } ] } {code}
> As seen above, Line number should have been returned as 3, but it is returned
> as 2.
> This probably is happening because we intrinsically ignore the first line in
> the template file
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
