Entity Update Profile¶
The performance of programmatically updating existing entity instances.
The Open Metadata Repository Services (OMRS) interface for a metadata repository defines optional methods for updating entity instances:
||changes one or more values of the properties on an existing entity|
||changes the status of an existing entity|
||See (2) in detailed logic below.|
||See the detailed logic of the entity retype profile.|
Captures timestamp for historical metadata profiles
Prior to this profile running, a timestamp is captured by the performance workbench to denote a specific date and time prior to any updates having been made to the entities.
For every entity type supported by the technology under test, this profile does the following (in order):
- Searches for
instancesPerTypeentities of that type. (This uses
findEntitiesByPropertywith a condition on
metadataCollectionIdand its performance is recorded as part of the entity search profile.)
- For each of these entity instances,
updateEntityPropertiesis called to update the existing property values of the entity, using a new generated set of properties.
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
findEntitiesByProperty 50 times.)
The properties of each of these instances will be fully-populated with:
- Any string properties containing a value representative of the property name itself (and where unique, they will be made unique through appending a unique sequence)
- Any non-string properties will be randomly generated, in a simple attempt to represent data that is not entirely uniform
Note the following caveats:
updateEntityStatusis currently not tested (there are very few types that support any status that can be updated outside of a delete or restore operation).
- Entity type definitions that have no properties will not be updated, since there are no properties to update.