Entity Undo Profile¶
The performance of programmatically reversing the latest update to an existing entity instance.
The Open Metadata Repository Services (OMRS) interface for a metadata repository defines an optional method for reverting updates on entity instances:
| Method | Description |
|---|---|
undoEntityUpdate |
reverts the last update that was made to an entity |
Assertions
| ID | Description |
|---|---|
repository-entity-undo-performance-undoEntityUpdate |
See (2) in detailed logic below. |
For every entity type supported by the technology under test, this profile does the following (in order):
- Searches for
instancesPerTypeentities of that type that have at least one change. (This usesfindEntitieswith a condition on bothmetadataCollectionIdandversionbeing greater than1, and its performance is recorded as part of the entity search profile.) - For each of these entity instances,
undoEntityUpdateis called to revert the last change.
Example
So, for example, if the technology under test supports 50 entity types, and the instancesPerType parameter is set to 100, then this profile will update 50 (types) x 100 (instances per type) = 5000 entities. (And it will run findEntities 50 times.)
Raise an issue or comment below