Catalog

Last updated 10/03/2026

The Catalog module provides one-stop management of all table assets in the space, as well as centralized viewing and organizing of space resources.

• Assets: owned by the DataOps space, which has full management rights over them. They can be authorized to other entities (such as spaces and projects) for use as data resources.
• Resources: usable by the DataOps space, but owned by other entities.

Feature area overview

Feature area	Sub-feature	Description
1 - Feature switching area	Table Management	The core feature of the Catalog module. You can view and manage the following in the space: Task tables (ws_default_${env}) IDE tables (ws_default_ide) Tables authorized by external spaces (ws_xxx_${env}, ws_xxx_ide) Authorized system tables (ta, ta_dim, ta_ext)
	Link Management	In this area, you can Batch Create link view tables Or view the batch creation records in the space
	Recycle Bin	Recycles soft-deleted workspace tables from Table Management Tables are permanently deleted after being kept in the recycle bin for 7 days
	Unregistered Table	In Table Management, tables in the space's development/production dual databases have a "registration status": Registered: task tables created through the space's Catalog UI Unregistered: the table exists on the engine side (for example, created with create table in the IDE module) but wasn't created through Table Management. You need to fill in the missing information to complete registration and make sure the table works properly. Scenarios that may cause a table to be "unregistered" Creating a table in a node script of a Flow Creating a table in the IDE module Connecting directly to Trino through the DataOps Platform and creating a table with the command line or database software
2 - Dictionary area	View by warehouse	Organizes the table assets and table resources managed by the Catalog module in the space, making them easy to find and manage Shows the structure of the AE built-in warehouse as a tree, based on the four elements of a table The dual-environment databases of the AE built-in warehouse are shown in the dictionary area as: ws_default_${env}
3 - Tab area	Tab display	When you first enter the Catalog module, the "Table Management" tab is shown by default. It can't be closed or reordered You can view multiple table details tabs at the same time ⚠️ Note: You can't open multiple new table pages at the same time
4 - Page content area	Table Management page	A permanent tab that lets you quickly search and view table information
	Table details page	Shows table details, such as metadata, fields, DDL, and data preview
	Table creation/editing page	On the creation page, select the management mode and table type to create the corresponding workspace table
5 - Drawer area	Quick view	Opened quickly from the management page to show the table's key information

Create tables and views

Click + Table in the upper-right corner of the Table Management page to open the new table page.

You can choose to create a space Table or View. For details about creating workspace tables, see the Workspace tables section.

Table Management

Schema area

The dictionary area of Table Management shows all assets and resources available in the space using the Catalog - db - table structure under each warehouse.

The dictionary area counts and shows the number of tables/views in each database according to this structure. When you select a database name in the dictionary area, the list area shows the tables in that database.

Tips: Within the AE built-in warehouse, the available

• System table scope must be obtained through Project Authorization
• External space resources scope must be obtained through Data authorization between spaces

The structure of the dictionary area is described below:

Legend	Warehouse (repo)	Catalog	Management Mode	Database (db)	Description
	Built-in ETL warehouse	hive	System table	ta	AE system database, including user snapshot tables, tag and cohort tables, and more
				ta_dim	AE system database, including project dimension tables
				ta_ext	AE system database, including project data tables
				temp	AE system database, including SQL IDE temporary tables of projects
			Workspace-Task table	ws_space_${env}	Dual-environment databases of the DataOps Platform
			Workspace-IDE table	ws_space_ide	IDE database of the DataOps Platform
			External authorized table	ws_otherspace_product	Production environment databases authorized to this space by external spaces
				ws_otherspace_ide	IDE databases authorized to this space by external spaces

List display

In the table list area, you can view:

• The four elements of a table: Warehouse - Catalog - Database name - Table name
• Table management mode
• Table owner
• Table registration status
• Drill down to view table details
• Search 🔍: search by table name and table comment

Filtering

On the table list page, you can filter tables by key fields:

• The filter panel is collapsed by default and can be expanded or collapsed
• You can reset the filters

Filter type	Filter	Options	Description
Checkbox	Changed	-	Only for "Workspace-Task table": the development environment has changes compared with the production environment
	I owned	-	Owner = the currently logged-in user
	Expiring Soon	-	Tables whose lifecycle is about to expire
	Unpublished	-	Tables that exist only in the development environment and haven't been released to the production environment
Multi-select	Management Mode	Workspace-Task table Workspace-IDE table System table External authorized table	Categorized by the table's management mode in the space
	Table Type	Table View
	Owning entity	Space name Project name	The owning entity of a System table is a project The owning entity of an External authorized table is another space
	Responsible person	Owner of the table	The owner of System tables defaults to: System The owner of External authorized tables isn't shown

Batch operations

The table list page (including drill-down list pages) supports batch operations.

The objects on which operations can be performed are as follows:

Batch operations	Supported management modes	Scope supported for batch operations
Renew	Workspace-Task table	Registration status = Registered AND Table type = Physical table
Release	Workspace-Task table	Registration status = Registered AND (Release status = Unpublished OR Changed = Changed)
Recycle	Workspace-Task table	Registration status = Registered (unregistered tables can't be moved to the recycle bin) Note: Workspace-IDE tables can't be recycled yet

Drawer area

Click a table card on the management page to open the table details drawer on the right

• Quickly browse the table's Meta and field information on the current page to find tables more efficiently
• Open it without opening a new tab, which keeps the number of tabs down

Content

Area	Content	Visible management modes	Description
A	Environment switcher	Workspace-Task table	Switch between development environment and production environment tables
B	Unregistered notice	Workspace-Task table Workspace-IDE table	Click the edit button to open the table edit page. Saving completes the registration
C	Warehouse/catalog/database information	All	View the schema elements that the workspace table belongs to
D	Management information	All	Includes Management Mode: the management mode of the current workspace table Related Task (Workspace-Task table) Owning entity: space/project name Status: When the management mode is "System table", "External authorized table", or "Workspace-IDE table", it's always "Online" When the management mode is "Workspace-Task table", it depends on the table's release status
E	Storage Method	All	Storage Type: Internal Table/External Table. System tables default to Internal Table Storage Format: System tables default to ORC Storage Method: System tables default to HDFS Storage Path: the storage path of the workspace table Storage size: the amount of storage used
F	Owner	All	Defaults to "System" for System tables
	Remarks	All	Shows "-" if empty
	Lifecycle Days	Workspace-Task table Workspace-IDE table	Shown as "-" for unregistered tables
	Lifecycle Status	All	Defaults to "Normal" for System tables / External authorized tables; shown as "-" for unregistered tables
G	Creator	All	Defaults to "System" for System tables
	Created at	All	Creation time of the workspace table
	Last Releaser	Workspace-Task table	Release information of the workspace table
	Last Releasing time
H	Field information	All	Table fields and field data types
I	DDL	All	DDL statement (not shown for System tables)

Link Management

Link is a signature feature of the AE DataOps Platform. It lets you quickly migrate your enterprise's internal data system to the AE system.

The Link feature mainly uses Trino's Connector capabilities. With it, you can use tables in custom Catalogs mounted to AE Trino as base tables to create views that can be used in workspaces. In the DataOps Platform, these views are called Link Views.

Link views can be used in DataOps Platform spaces, and can also be authorized to other entities in the AE system through DataApp - Data Authorization, such as projects in Analytics & Engage or other DataOps spaces.

tip

To use the Link feature, first contact ThinkingAI staff to configure the Catalog.

Batch create link views

When you want to create link views for all data in a whole database to quickly bring in your existing data system, click + Link View in the upper-right corner of the Link Management page to create them in batches. For the steps, see Batch create link views.

In addition, a Link View is a special type of view in the DataOps Platform: its source base tables are tables in a Catalog that is externally mounted to the AE built-in warehouse through a Trino connector.

So to create a single "link view", follow the same steps as creating a regular view. For details, see Workspace tables.

Recycle Bin

Click the third icon in the left toolbar of the Catalog module to open the recycle bin list of workspace tables.

About the recycle bin:

• Stores recycled production/development environment workspace tables. The data is retained but can't be read or written

• Supported operations:

  • Restore: re-enable the table
  • Permanently Delete: completely clear the data

• The system automatically cleans up tables that have been left unhandled for too long (stored for more than 7 days)

• Batch restore/delete is supported for higher efficiency

Column name	Description
Table Name	Name of the workspace table. Click it to open the details page of the workspace table in the recycle bin
Comment	User-defined description of the table
Type	Type of the workspace table: table or view. Filterable
Engine	Query engines that can query the workspace table. There may be multiple engines. Filterable
Recycle Reason	Why the workspace table was recycled: recycling after expiration or manual recycling. Filterable
Recycling Time	When the workspace table was recycled
Remarks	User-defined remarks
Action - Restore	Click to restore the workspace table so you can continue to access or write to it normally
Action - Permanently Delete	Click to permanently delete the workspace table. Permanent deletion can't be undone, so proceed with caution

Unregistered tables

Definition of "unregistered tables"

In Table Management, tables in the space's development/production dual databases have a "registration status":

• Registered: task tables created through the space's Catalog UI
• Unregistered: the table exists on the engine side (for example, created with create table in the IDE module) but wasn't created through Table Management. You need to fill in the missing information to complete registration and make sure the table works properly.

Manage "unregistered tables"

If there are unregistered tables in the space, the fourth Tab button in the left toolbar of Catalog is highlighted and shows the number of unregistered tables

• If the count is 0, it isn't shown
• If the count exceeds 9, 9+ is shown

Entry point

Management page

Column name	Description
Table Name	Name of the unregistered table
Warehouse	Built-in Warehouse
Data catalog	Catalog that the unregistered table belongs to
Database	ws_default_${env} is the dual-environment task database of the DataOps Platform
Dual environments	An unregistered table may exist only in the production environment or only in the development environment, or in both environments but inconsistently Therefore Gray means there's no unregistered table in that environment Production means there's an unregistered table in the production environment Dev means there's an unregistered table in the development environment
Related Task	Tasks in Flows that use the current unregistered table as the "Target table"
Created at	When the unregistered table was created
Action	Register Register by Development Environment: registers the table to the production environment based on the development environment's table structure Register By Production Environment: registers the table to the development environment based on the production environment's table structure Delete

Scenarios that produce "unregistered tables"

The following actions in a DataOps Platform space may produce unregistered tables

Module	Feature area	Database	Table/view	Handling
IDE	Script	Hive.dev database of this space	Create view	Goes to "Unregistered Table"
		Hive.pro database of this space	Create view	Goes to "Unregistered Table"
		Hive.ide database of this space	Create table Create view	Not registered or scanned
Development	SQL node	Hive.dev database of this space	Create table Create view	Goes to "Unregistered Table"

Registration process

Case 1: The table exists only in the development environment

Use Register by Development Environment

• After registration, the existing table (development environment) and its data are retained
• After registration, the table is in the Unpublished status

Case 2: The table exists only in the production environment

• After registration, the existing table (production environment) and its data are retained, and a table with the same structure is created (development environment)
• After registration, the table is in the Online status

Case 3: The table exists in both the development & production environments

• You need to choose which table to keep

• Option 1: Keep the development environment

  • Keep the table and data in the development environment, and delete the table and data in the production environment
  • Create a production environment table with the same structure

• Option 2: Keep the production environment

  • Keep the table and data in the production environment, and delete the table and data in the development environment
  • Create a development environment table with the same structure

• After registration, the table is in the Online status