Hello All, I was assigned to platform support of my company's Collibra DQ environments about 6 months ago. So far, so good, but I believe that we might have some minor issues related to the metastore component( external postgres flexible server, "cloud native" Azure Kubernetes agent/web/livy/spark config). The largest objects in the database by far are the following: data_preview rule_breaks validate_source_value assignment_q_audit assignment_q observation We are currently on version 2025.04-ABDGCSHILM-4254. These environments were stood up several years ago by engineers who are no longer at our company. I'm still moving up the learning curve with this platform, but I don't believe that anything was configured beyond defaults for data retention. I recently set the Data Retention Policy to "By Time / By Run Date(run_id) / 120 Days." I just wanted to get some feedback on metastore best practices and determine whether there is any "bloat" in our metastore databases that require attention. This might not be a major issue, but I have observed a query against the rule_breaks table(with no WHERE clause) that has run 19 times over the past 28 days with an execution times ranging between 1.5 minutes and 43 minutes. I have also noticed a query against the rule_breaks table that has executed 20 times in the last 28 days with exec times ranging between 8 and 25 minutes: --rule breaks long running sql -- SELECT "public"."rule_breaks"."dataset", "public"."rule_breaks"."run_id", "public"."rule_breaks"."rule_nm", "public"."rule_breaks"."link_id" FROM "public"."rule_breaks" -- validate source id long running sql -- select id, CAST(uuid AS VARCHAR(255)) UUID , validate_source_id, cast(validate_source_uuid AS VARCHAR(255)) as validate_source_uuid, assignment_id, cast(assignment_uuid AS VARCHAR(255)) as assignment_uuid , obs_sub_type , key_col_nm , key_col_value, target_link_id, source_link_id, target_col_nm, target_col_value, source_col_nm, source_col_value, confidence , cnt from public.validate_source_value
