How to Filter Tables in the YBA xCluster Disaster Recovery Tables Tab

How to Filter Tables in the YBA xCluster Disaster Recovery Tables Tab

Environment

YugabyteDB Anywhere — all versions with xCluster or xCluster Disaster Recovery configured

Issue

The YBA xCluster Disaster Recovery Tables tab has a search bar that supports both basic substring search and advanced column-specific filtering. The modifier syntax is not displayed in the UI. Use the syntax in this article to filter by table name, schema, database, size, replication status, or replication lag.

Overview

The Tables tab search bar accepts two modes:

1. Basic search — type any string with no modifier. YBA performs a case-insensitive substring match across four columns: Table Name, Schema Name, Database, and Replication Status.
2. Modifier search — type modifier:value to filter on a specific column. Press Enter or click outside the search field to commit the filter as a chip.

Press Enter or Tab to commit the input as a chip. Clicking outside the search field does not commit it.

Multiple modifiers applied in the same session are joined by AND. There is no OR or grouping support.

Navigating to the Tables Tab

1. Open YugabyteDB Anywhere and go to the universe.
2. Select xCluster Disaster Recovery from the left nav or the universe detail page.
3. Click the Tables tab (next to Metrics).

The search bar appears above the table list.

Basic Search

Type any string into the search bar without a modifier keyword.

example_table_name

YBA returns all rows whose Table Name, Schema Name, Database, or Replication Status column contains that string (case-insensitive, substring).

Advanced Filter Modifiers

To filter on a specific column, use:

modifier:value

Type the modifier and value, then press Enter or Tab to commit.  The value becomes a chip. Remove a chip by clicking the × on it.

 sizeBytes and replicationLagMs require an explicit comparison operator. A bare number, for example sizeBytes:0, matches no rows. Use sizeBytes:=0 instead. Values must be non-negative integers.

sizeBytes and status apply only to tables with table info available. replicationLagMs applies only when a lag value is reported for that table. A table missing that data will not match the corresponding modifier, including replicationLagMs:=0.

Status Values

The status modifier matches the display label shown in the Replication Status column:

status:Error does not match error tables. For a table with a specific replication error, the searchable text is the error message itself, not the word "Error." Search the error text directly instead, for example:

status:Schema mismatch
status:Missing op ID
status:Source unreachable

Other error labels you may need to search for: Unknown error, Missing table, Uninitialized, Auto flag config mismatch, System error

Numeric Filter Operators

The sizeBytes and replicationLagMs modifiers accept comparison operators:

Combining Filters

Multiple modifiers narrow the result set. Each modifier added applies as an AND condition.

status:Validated database:mydb

Returns all Validated tables in the mydb database.

sizeBytes:=0 status:Operational

Returns all Operational tables with 0 bytes.

There is no OR, (, or ) support. To search across disjoint values, run separate queries.

Sorting

Click any column header to sort ascending or descending.

Useful combinations:

• Size ascending — surfaces all 0-byte tables (partitions added before data was written).
• Current Lag descending — surfaces the most stale tables first.
• Table Name ascending — groups partitions sharing a naming pattern for visual scanning.

Common Workflows

Find all non-Operational tables

There is no single filter that returns every non-Operational table. Each specific error is searchable only by its own error text, not by the word "Error." Run separate queries for the statuses you want to check:

status:Validated
status:Failed
status:Warning
status:In Progress
status:Bootstrapping

For a table currently showing a specific error, search the error text directly:

status:Missing op ID

Find all tables with no replication lag

replicationLagMs:=0 status:Operational

Find all tables with no replication lag

replicationLagMs:=0 status:Operational

Find all partitions matching a name pattern

table:partial_table_name

Narrow to a specific status:

table:partial_table_name status:Validated

Find zero-byte tables

sizeBytes:=0

Then sort by Table Name to group by partition date.

Find high-lag tables

replicationLagMs:>30000

Returns tables with lag over 30 seconds. Adjust the threshold to match your RPO.

Find tables in a specific schema

schema:public

Screenshots

The following are visual examples of using the filters.

Tables tab — default state (empty search bar, full table list)

The Tables tab showing all replicated tables. Columns: Table Name, Schema Name, Database, Size, Replication Status, Current Lag.

Table Filtering

After typing table:with_ddls and pressing Enter, the value becomes a chip. The list shows only tables whose name contains that substring.

Filtering on Size

sizeBytes: modifier being typed

Typing sizeBytes: in the search bar before specifying a value. The full table list remains visible until a value is committed.

Filtering on Replication Lag

replicationLagMs: modifier being typed

Typing replicationLagMs: in the search bar. Append a comparison operator and value (e.g., <20) before pressing Enter.

replicationLagMs:<20 filter committed — filtered results

After committing replicationLagMs:<20 as a chip, the list shows only tables with current lag under 20 ms. Tables with higher lag are excluded.

Combined filters with no matching rows — AND logic

Two chips active: table:with_ddls and status:error. No tables match both conditions. The table list shows "There is no data to display."

Known Limitations

• Extra Table On Source/Target and Dropped From Source/Target statuses match unexpected substrings. The searchable text for these statuses is currently generated incorrectly and does not match the display label. Searching extra matches Extra Table On Source/Target rows, but searching extra table does not. Unrelated words such as object or string may also incidentally match these rows. 

  Improvements in PLAT-21462.

• Only the first error is searchable when a table has more than one active replication error at once. Additional simultaneous errors on the same table are not matched by status: search. T

  Tracked in PLAT-21470.

• Advanced search modifiers are a newer capability with limited internal usage to date. If a filter returns unexpected results, cross-check against the column values directly, or use basic search instead.

Quick Reference

# All tables matching a name pattern
table:partial_table_name

# All Validated tables in a specific database
status:Validated database:mydb

# Tables with lag over 1 minute
replicationLagMs:>60000

# Zero-byte tables
sizeBytes:=0

# All tables in a specific schema
schema:public

# Combined: specific partitions not Operational
table:partial_table_name status:Validated

Filter Behavior Summary

• No modifier: substring match across Table Name, Schema Name, Database, Replication Status.
• With modifier: match on that column only.
• sizeBytes and replicationLagMs require an explicit operator (=, !=, >, <, >=, <=). A bare number matches nothing.
• status:Error does not match error-state tables. Search the specific error text instead.
• Multiple modifiers: AND (every active chip must match).
• Chips: committed filters shown as dismissible pills above the search bar. Press Enter or Tab to commit, not by clicking outside the field.
• Case-insensitive for all string modifiers.