Current connector implementation stores batch processing state (lastSyncDate) based on the unique key (governance rule name) that is composed of the configuration parameters for given proxy instance.
Example:
"Job metadata will be synced through Egeria (JOB_LEVEL) for projects: [MY_ETL_PROJECT]"
This does not allow uses (for advanced deployment) to run and sync multiple independed proxy instances.
One possible improvement will be use metadataCollectionId from the proxy repository as key (or append it to the existing composite key / governance rule name).
Current connector implementation stores batch processing state (lastSyncDate) based on the unique key (governance rule name) that is composed of the configuration parameters for given proxy instance.
Example:
"Job metadata will be synced through Egeria (
JOB_LEVEL) for projects: [MY_ETL_PROJECT]"This does not allow uses (for advanced deployment) to run and sync multiple independed proxy instances.
One possible improvement will be use
metadataCollectionIdfrom the proxy repository as key (or append it to the existing composite key / governance rule name).