[ATLAS-931] Delete entities fails when hard delete is configured

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 0.7-incubating
• Assignee: Dave Kantor
• Reporter: Prasad S Madugundu
• Created: 21/Jun/16 13:37
• Updated: 22/Jun/16 00:51
• Resolved: 22/Jun/16 00:51

Description

When Atlas is configured for hard deletes, entity deletion fails with an EntityNotFoundException when retrieving a deleted entity to include in the response. This occurs when the delete operation does not update any objects, so that the list of updated guids returned by the service layer is empty and EntityResource uses a deleted entity guid to retrieve the "sample" entity definition to include the response. If hard delete is enabled, the entity no longer exists and the entity lookup fails.

SEVERE: Could not find an entity in the repository with __guid = d7b21c03-e518-44ed-83d3-2593e9c50dd1,
com.ibm.analytics.oms.exception.AtlasException: Could not find an entity in the repository with __guid = d7b21c03-e518-44ed-83d3-2593e9c50dd1,

Caused by: org.apache.atlas.typesystem.exception.EntityNotFoundException: Could not find an entity in the repository with __guid = d7b21c03-e518-44ed-83d3-2593e9c50dd1,
at org.apache.atlas.repository.graph.GraphHelper.findVertex(GraphHelper.java:183)
at org.apache.atlas.repository.graph.GraphHelper.getVertexForGUID(GraphHelper.java:301)
at org.apache.atlas.repository.graph.GraphBackedMetadataRepository.getEntityDefinition(GraphBackedMetadataRepository.java:146)
at org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)
at org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:371)
at org.apache.atlas.web.resources.EntityResource.getResponse(EntityResource.java:171)
at org.apache.atlas.web.resources.EntityResource.deleteEntities(EntityResource.java:388)