Hi,
I have created a simple monitoring project with 12 catalog items for which I do only one dq check per catalog item + anomaly detection for this one attribute. However it seems that for this the system runs a full profile of every catalog item. Therefor this project is very heavy for the system to process. Can we adjust some settings so that the profiling is only run for this one attribute per table? Seems like a waste of resources this way.
kind regards, Jur Dördregter
From my recollection, the default processing plan for running a monitoring project is to run a full profile on that catalog item. To stray away from effecting other monitoring projects, and changing the underlying plan of kicking off monitoring projects, I would recommend creating Custom SQL Catalogs that only pull in the attributes that are needed for profiling / monitoring.
This will help with unnecessary heavy profiles and processing times, and keep the underlying ataccama processes running the same.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.