Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
trunk
-
None
Description
Scenarios
Case 1
In a situation where, data exported from a cluster is imported to a different cluster, it is necessary to make changes to attributes of entities such that their values represent their environment
Example: Entities exported from cluster called 'cl1' will have @cl1 in their qualifiedName attribute. When these entities are imported to a cluster called 'cl2' the qualifiedName attribute should read @cl2 to correctly reflect their new environment.
Case 2
Exported data contains an attribute that has value that does not conform to the conventions followed within the cluster. This can be corrected by exporting the data and reimporting it with an applied transform.
Example: Entities were created with an attribute value as upper case, this needs to be lower case to conform to a convention.
Solution
As part of Import API, it will help to be able to specify in a generic manner the transforms that could be applied to an entity type.
The implementation should be extensible so that new transforms could be added in future.
Attachments
Attachments
Issue Links
- links to