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

[Atlas: Glossary Term Bulk Import] Need a way to know if the import was fully success or partial success or failure

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      When there are partial success the response need to convey the details clearly to the user

      Partial import example:

      While importing bulk glossaries via bulk import feature, if one of the rows has a fault, it throws exception and creates only glossary names for the rest of the input without creating the associated terms

      Consider the following input

      GlossaryName, TermName, ShortDescription, LongDescription, Examples, Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor, Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso, TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
      gloss_1,term_1
      gloss_1,term_1
      gloss_2,term_2
      gloss_3,term_3
      
      

      Here we are creating gloss_1 and term_1 twice.

      The first time succeeds, the second time it throws the right exception as follows

       {"errorCode":"ATLAS-500-00-016", "errorMessage":"Error occurred while creating glossary term: \{0}
      ",
      "errorCause":"Glossary term with qualifiedName term_1@gloss_1 already exists"}

       

      But for the remaining rows, it creates only the glossaries without creating the terms

      The import call fails but still data is populated which leads to confusion. There is no way to know if the import was fully success or partial success or failure 

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            mayank_nj Mayank Jain
            dharshmk Dharshana M Krishnamoorthy
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment