Skip to main content

Define Scopes

Scopes are reusable table selectors that determine which tables are included in or excluded from monitoring and replication operations.

Create a Scope​

  1. Navigate to Iceberg > Scopes
  2. Click Add New Scope
  3. Enter a Name (e.g. all-analytics-tables)
  4. Enter the Namespace — the exact, case-sensitive namespace name as it appears in the catalog
  5. Choose the Match type:
    • By Name — matches a single table by exact name
    • By Pattern — matches tables using a regular expression
  6. Enter the Value — either the table name or the regex pattern
  7. Click Create

Pattern Examples​

NameNamespaceMatch typeValueWhat it matches
All analytics tablesanalyticsPattern.*Every table in the analytics namespace
Orders table onlysalesNameordersOnly the orders table in sales
All customer tablessalesPatterncustomer.*Tables starting with "customer" in sales
Exclude stagingstagingPattern.*Every table in staging (use as exclusion scope)

Patterns use Java regular expression syntax. The pattern is matched against the table name only, not the fully qualified namespace.table path.

Use Scopes in Monitors and Replications​

When creating a monitor or replication, you attach scopes in two roles:

  • Inclusion scopes — tables matching any inclusion scope are processed
  • Exclusion scopes — tables matching any exclusion scope are skipped, even if they match an inclusion scope

Exclusion takes priority over inclusion. If a table matches both an inclusion and an exclusion scope, it is skipped.

Edit a Scope​

  1. Open the scope from Iceberg > Scopes
  2. Modify the name, namespace, match type, or value
  3. Click Save

Changes to a scope affect all monitors and replications that reference it.

Delete a Scope​

  1. Open the scope from Iceberg > Scopes
  2. Click Delete Scope

A scope cannot be deleted if it is referenced by an active monitor or replication. Remove those references first.

Tips​

  • Use the catalog Content browser to find the exact namespace names before creating scopes
  • Create broad inclusion scopes (e.g. .* for a namespace) and narrow exclusion scopes to skip specific tables
  • Give scopes descriptive names — they appear in the monitor and replication configuration and should be easy to identify