All ideas are welcome. Just because the Idea doesn't make it into the product immediately does not make it a bad idea.
Some scenarios are not covered by the API in Metadata discovery 1.3.
Field removal: field is not removed
Field length change: field is not updated
Field type change: field is not updated
Description change at system type level: field is duplicated
I´ve attached some samples of the issue watched .
If the API could transfer these changes to the KT, we would get a full alignment in cases of changes of metadata in source system
Guest
These scenarios are being supported, not by API but rather by the cloud native/ agent based scanning capabilities being added to the catalog in ~Q3 2022
