Removal or alias change of a schema from a mapping

[camemre49]

When multiple schemas are added to a mapping and their source contexts are defined, removing a schema from the mapping does not automatically remove the associated source context in the job. This leads to conflicts between the remaining source contexts and schemas in the mapping. To resolve this, the related source context should be deleted from all jobs that include the mapping whenever a schema is removed from that mapping. A similar issue is encountered on schema alias change .

Possible scenarios:

• Schema alias renamed from schema management -> After updating mapping, update all FhirMappingTasks inside jobs using that mapping so that they match with updated alias.
• A schema removed from schema management -> Find all jobs using that mapping and remove corresponding FhirMappingSourceContext from FhirMappingTask s
• A new schema added from schema management -> Add FhirMappingSourceContext inside each FhirMappingTask with new schema alias to all jobs using that mapping.

[camemre49]

According to the README file, the data source names of a job, source context names of a job, and schema aliases of mappings included in that job must be identical. However, since a job can have multiple mappings and a mapping can be included in multiple jobs, names must be maintained continuously. Some possible solutions:

• Remove the naming requirement and match sources by their order in job configurations, or
• Store two separate names: one for schema aliases in mappings and one for source context and data source names in jobs.