Uploaded image for project: 'Atlas'
  1. Atlas
  2. ATLAS-4311

[Business Metadata Bulk Import] Wrong Line Number returned in failedImportInfoList

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.0.0, 2.2.0
    • Component/s: atlas-core
    • Labels:
      None

      Description

      The api/atlas/v2/entity/businessmetadata/import returns the incorrect Line Number

      For instance, following is the data in template file 

      EntityType,EntityUniqueAttributeValue,BusinessAttributeName,BusinessAttributeValue,EntityUniqueAttributeName[optional] 
      hive_table,hive_table_kcsup@cm,BM3.BM3A1,stringval 
      hive_table,invalid_table@cm,BM3.BM3A1,stringval  

      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 

      { "failedImportInfoList": [ { "parentObjectName": "", "childObjectName": "", "importStatus": "FAILED", "remarks": "Line #2: no hive_table entity found with qualifiedName=invalid_table@cm" } ] }  

      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

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                radhikak Radhika Kundam
                Reporter:
                umesh.padashetty Umesh Padashetty
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: