[ATLAS-3050] OGM DataAccess: Error Condition Change

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.8.3, 2.0.0
• Fix Version/s: 0.8.3, 2.1.0
• Component/s: atlas-core
• Assignee: Ashutosh Mestry
• Reporter: Ashutosh Mestry
• Created: 15/Feb/19 17:59
• Updated: 09/Aug/19 04:41
• Resolved: 09/Aug/19 04:41

Description

Background

The DataAccess.saveNoLoad method uses contents of EntityMutationResponse to detect error condition. This is unnecessary as AtlasEntityStore.createOrUpdate does the necessary error handling.

Steps to Duplicate

1. From Atlas UI, create a hdfs_path entity, say /warehouse/hr@cl1
2. Export using the attached export-options.json. These options will force the creation of AtlasServer entity.
3. Export succeeds.
4. 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, <guid>.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}}, urls=null}

        at org.apache.atlas.repository.ogm.DataAccess.saveNoLoad(DataAccess.java:56)

        at org.apache.atlas.repository.ogm.DataAccess.save(DataAccess.java:45)

        at org.apache.atlas.repository.impexp.AtlasServerService.save(AtlasServerService.java:93)

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