[ATLAS-2805] Update Classification: Does Not Update modificationTimestamp

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.8.3
• Fix Version/s: 0.8.3, 1.2.0, 2.0.0
• Component/s: atlas-core
• Assignee: Ashutosh Mestry
• Reporter: Ashutosh Mestry
• Due: 03/Aug/18
• Created: 02/Aug/18 16:33
• Updated: 26/Sep/19 00:38
• Resolved: 06/Aug/18 20:22

Description

Background

Existing implementation of EntityGraphMapper.addClassifications does not update modificationTimestamp. 

This causes inconsistency if entities are fetched using modificationTimestamp. 

Steps to Duplicate

Pre-requisites: Setup an instance with few entities. Create classifications, say PII. Do not associate any entity with classification.

Steps:

1. Search an entity and display it in web UI. Note the modificationTimestamp.
2. Associate the entity above with PII classification.
3. Refresh the web page. Notice that the  modificationTimestamp is unchanged.

Approach Guidance

• EntityGraphMapper should have 2 public methods that explicitly state their purpose. Say addClassifications and addClassificationWIthNoMetadataUpdate.
• The addClassifications will update the modificationTimestamp, the other will not.
• RequestContextV1 should be updated to have a request the ability to update or not update timestamp. This should be checked in the method: updateModificationMetadata.