[jira] [Commented] (ATLAS-4130) [Atlas: Glossary Term Bulk Import] Need a way to know if the import was fully success or partial success or failure
[
https://issues.apache.org/jira/browse/ATLAS-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17312656#comment-17312656
]
ASF subversion and git services commented on ATLAS-4130:
Commit b5b6ca0e8d09fae070aa3555373f2946892057bd in atlas's branch
refs/heads/branch-2.0 from mayanknj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=b5b6ca0 ]
ATLAS-4129: Glossary Bulk Import Bugs consolidated fix (ATLAS-4128, ATLAS-4131,
ATLAS-4160, ATLAS-4130, ATLAS-4129)
Signed-off-by: Sarath Subramanian
(cherry picked from commit 842890d27bf739a0949e82b58d9db1f1dd6111ea)
> [Atlas: Glossary Term Bulk Import] Need a way to know if the import was fully
> success or partial success or failure
> ---
>
> Key: ATLAS-4130
> URL: https://issues.apache.org/jira/browse/ATLAS-4130
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mayank Jain
>Priority: Major
> Attachments: Screenshot 2021-01-28 at 11.46.10 AM.png
>
>
> 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
> {code:java}
> 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
> {code}
> Here we are creating gloss_1 and term_1 twice.
> The first time succeeds, the second time it throws the right exception as
> follows
> {code:java}
> {"errorCode":"ATLAS-500-00-016", "errorMessage":"Error occurred while
> creating glossary term: \{0}
> ",
> "errorCause":"Glossary term with qualifiedName term_1@gloss_1 already
> exists"}{code}
>
> 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
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4130) [Atlas: Glossary Term Bulk Import] Need a way to know if the import was fully success or partial success or failure
[
https://issues.apache.org/jira/browse/ATLAS-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17312648#comment-17312648
]
ASF subversion and git services commented on ATLAS-4130:
Commit 842890d27bf739a0949e82b58d9db1f1dd6111ea in atlas's branch
refs/heads/master from mayanknj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=842890d ]
ATLAS-4129: Glossary Bulk Import Bugs consolidated fix (ATLAS-4128, ATLAS-4131,
ATLAS-4160, ATLAS-4130, ATLAS-4129)
Signed-off-by: Sarath Subramanian
> [Atlas: Glossary Term Bulk Import] Need a way to know if the import was fully
> success or partial success or failure
> ---
>
> Key: ATLAS-4130
> URL: https://issues.apache.org/jira/browse/ATLAS-4130
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mayank Jain
>Priority: Major
> Attachments: Screenshot 2021-01-28 at 11.46.10 AM.png
>
>
> 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
> {code:java}
> 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
> {code}
> Here we are creating gloss_1 and term_1 twice.
> The first time succeeds, the second time it throws the right exception as
> follows
> {code:java}
> {"errorCode":"ATLAS-500-00-016", "errorMessage":"Error occurred while
> creating glossary term: \{0}
> ",
> "errorCause":"Glossary term with qualifiedName term_1@gloss_1 already
> exists"}{code}
>
> 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
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
