[
https://issues.apache.org/jira/browse/ATLAS-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Mestry updated ATLAS-2805:
-----------------------------------
Attachment: ATLAS-2805-Add-Classification-does-not-update-modifi.patch
> Update Classification: Does Not Update modificationTimestamp
> ------------------------------------------------------------
>
> Key: ATLAS-2805
> URL: https://issues.apache.org/jira/browse/ATLAS-2805
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 0.8.3
> Reporter: Ashutosh Mestry
> Assignee: Ashutosh Mestry
> Priority: Minor
> Fix For: 0.8.3
>
> Attachments: ATLAS-2805.2.patch
>
>
> *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:
> # Search an entity and display it in web UI. Note the
> _modificationTimestamp._
> # Associate the entity above with _PII_ classification.
> # 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_.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
