atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Mestry (JIRA)" <>
Subject [jira] [Created] (ATLAS-3050) OGM DataAccess: Error Condition Change
Date Fri, 15 Feb 2019 18:00:02 GMT
Ashutosh Mestry created ATLAS-3050:

             Summary: OGM DataAccess: Error Condition Change
                 Key: ATLAS-3050
             Project: Atlas
          Issue Type: Bug
          Components:  atlas-core
    Affects Versions: 0.8.3
            Reporter: Ashutosh Mestry
            Assignee: Ashutosh Mestry
             Fix For: 0.8.3


The _DataAccess.saveNoLoad_ method uses contents of _EntityMutationResponse_ to detect error
condition. This is unnecessary as _AtlasEntityStore.createOrUpdate_ does the necessary error

*Steps to Duplicate*
 # From Atlas UI, create a _hdfs_path_ entity, say _/warehouse/hr@cl1_
 # Export using the attached _export-options.json_. These options will force the creation
of _AtlasServer_ entity.
 # Export succeeds.
 # Perform step 2 again.

Contents of _export-options.json_

{ "itemsToExport": [ { "typeName": "hdfs_path", "uniqueAttributes": { "path": "/warehouse/hr/"
}} ], "options": { "replicatedTo": "clx" } }

Expected results:
 * Export should succeed with 4 files viz. _atlas-export-info.json, atlas-typesdef.json, atlas-export-order.json,


Actual results:
 * Export fails with server-side exception.


_org.apache.atlas.exception.AtlasBaseException: Save failed: \{guid=cd49c814-17f0-477f-805e-1944ccbcadf4,
name=clx, fullName=clx, displayName=clx, additionalInfo={REPL_DETAILS={"74b26dcb-c1af-4835-96dd-c36cc8f5bed0":1549943677980}},

        _at org.apache.atlas.repository.ogm.DataAccess.saveNoLoad(



        _at org.apache.atlas.repository.impexp.AtlasServerService$$FastClassBySpringCGLIB$$be2cd379.invoke(<generated>)_


This message was sent by Atlassian JIRA

View raw message