Documentation Index
Fetch the complete documentation index at: https://docs.open-metadata.org/llms.txt
Use this file to discover all available pages before exploring further.
Table Filter Patterns
Table filter patterns are used to control whether or not to include tables as part of metadata ingestion.- Include: Explicitly include tables by adding a list of comma-separated regular expressions to the Include field. OpenMetadata will include all tables with names matching one or more of the supplied regular expressions. All other tables will be excluded.
- Exclude: Explicitly exclude tables by adding a list of comma-separated regular expressions to the Exclude field. OpenMetadata will exclude all tables with names matching one or more of the supplied regular expressions. All other tables will be included.
Example 1
CUSTOMER within any schema and database. In this case we need to apply include table filter pattern ^CUSTOMER$. This will result in ingestion of tables Snowflake_Prod.SNOWFLAKE_SAMPLE_DATA.PUBLIC.CUSTOMER, Snowflake_Prod.SNOWFLAKE_SAMPLE_DATA.INFORMATION.CUSTOMER & Snowflake_Prod.SNOWFLAKE.PUBLIC.CUSTOMER
Configuring Filters via UI for Example 1

Configuring Filters via CLI for Example 1
Example 2
In this example we want to ingest table with nameCUSTOMER within PUBLIC schema of any database. In this case we need to apply include table filter pattern .*\.PUBLIC\.CUSTOMER$ this will also require to set the useFqnForFiltering flag as true as we want to apply filter on FQN. This will result in ingestion of tables Snowflake_Prod.SNOWFLAKE_SAMPLE_DATA.PUBLIC.CUSTOMER & Snowflake_Prod.SNOWFLAKE.PUBLIC.CUSTOMER
Configuring Filters via UI for Example 2

Configuring Filters via CLI for Example 2
Example 3
In this example, we aim to ingest a table named_delta_log/file.json within the session schema of any database. To achieve this, we need to configure the following filter patterns:
- Include Table Filter Pattern:
.*_delta_log/file\.json$ - Schema Filter Pattern:
session
Configuring Filters via UI for Example 3
