Metadb Table Exclusions

There is an ongoing effort to reduce the number of tables in the Metadb reporting database that are synchronized with FOLIO for updates to the data. This is done to improve the performance of Metadb overall. Also, some tables may be excluded to address problems impacting FOLIO applications.

List of Table Exclusions and General Notes from Index Data (from John Malconian)

• Index Data Metadb Table Exclusions December 2025 - This is the current Index Data Debezium table exclusion list.   It is not “authoritative” by any means or part of the Metadb project, and it is constantly evolving.
• We use a default schema inclusion list that includes the tenant schema prefix.   This effectively excludes anything outside the FOLIO tenant-specific schemas. So we use schema.include.list: "$TENANT_.*,id_dbz_$TENANT" where $TENANT is the tenant name (id_dbz_$TENANT is a Debezium heartbeat  table) as well as table.exclude.list  with the list of exclusions I posted above.

General Notes on Table Exclusions from EBSCO Hosting Team (from Carole Godfrey)

The sys_quartz_mod_scheduler table needed to be added to the table exclusion list for Metadb with Sunflower -- the issues is not a new type of issue

We need to exclude tables in metadb that contain arrays and or byte type data (since they cannot be processed by metadb)

This is a new global schema we observe in sunflower. 

So I believe simply excluding this is the solution

Also global schemas (in general) should be excluded from the sync/resync

This is the issue for supporting bytea data (which was observed in that table)

https://github.com/metadb-project/metadb/issues/88

Table Exclusion Notes for Cornell Metadb