Skip to main content

Overview

The Kinetica Virtual Catalog tables contain metadata about the database’s objects, relationships, & permissions. The tables are implemented commensurate with their usage and storage requirements. As such, a variety of distribution and partitioning schemes will be used across the tables. These tables will be automatically updated to reflect changes in the database structure and processing state. The information returned when querying the virtual catalogs is automatically filtered by the permissions of the querying user. For instance, regular users will only see the tables & views to which they have access when querying a virtual catalog table that lists all of the tables in the database, while system administrators will see all tables & views. For queries that can be run against the catalog tables to return useful information about the structure and processing state of the database, see Useful Catalog Queries. The Kinetica Virtual Catalog tables reside in the ki_catalog schema.

Catalog Table List

Catalog Column List

ki_backup_history

Each record in ki_backup_history represents a single backup or restoration event. It will include all types of backups and restorations from them.

ki_columns

Each record in ki_columns represents a single column in a table or view for all tables & views in the database, including those in virtual catalog tables.

ki_contexts

Each record in ki_contexts represents a top-level object within a SQL-GPT context. Objects can be one of the following:
  • Table Definition - Rules, samples & comments that apply to the use of the given table specifically
  • Rules Definition - Rules that apply globally when using the context
  • Samples Definition - Samples that apply globally when using the context

ki_datasinks

Each record in ki_datasinks represents a single data sink.

ki_datasource_subscriptions

Each record in ki_datasource_subscriptions represents a subscription a single target table has through a single data source.

ki_datasources

Each record in ki_datasources represents a single data source.

ki_datatypes

Each record in ki_datatypes represents a standard data type into which a supported data type can be translated. Not all supported data types will have a unique 1-to-1 mapping with the standard set, and not all data types listed in this table will have supported analogs in Kinetica.

ki_depend

Each record in ki_depend represents a dependent relationship between a “source” object and an object that depends on it; for example, a view will depend on all of the tables & views referenced in its corresponding query.

ki_fk_constraints

Each record in ki_fk_constraints represents a constrained column from either a primary key or foreign key relationship. For example, a table with a single primary key column will have one record in this table, while a composite foreign key linking two columns of one table to two columns of another will have two records in this table—one for each source-to-target column relation.

ki_functions

Each record in ki_functions represents a native scalar or aggregate function, a UDF/UDTF, or a SQL procedure.

ki_ha_consumers

Each record in ki_ha_consumers represents a process that consumes messages from the Kafka HA queues.

ki_indexes

Each record in ki_indexes represents a single index of a table with indexed columns.

ki_ingest_file_info

Each record in ki_ingest_file_info represents the import from a single data file into the database or the export into a single data file from the database.

ki_kafka_lag_info

Each record in ki_kafka_lag_info represents a partition of a subscription a single target table has through a single Kafka data source and the indexes of the most recently read message and most recently available messages on that partition.

ki_load_history

Each record in ki_load_history represents a process that was invoked during either the import into or export from the database. Multiple processes may be invoked for a single data processing task.

ki_obj_stat

Each record in ki_obj_stat represents a single table or view in the database and its associated sizing statistics, including those in virtual catalog tables.

ki_object_permissions

Each record in ki_object_permissions represents the mapping of a user or role to a system-level or object-level permission they have.

ki_objects

Each record in ki_objects represents a single table, view, or SQL procedure within the database, including those in the virtual catalog tables.

ki_partitions

Each record in ki_partitions represents a single partition of a partitioned table.

ki_periodic_objects

Each record in ki_periodic_objects represents a single materialized view or SQL procedure in the database with a periodic refresh/execution interval.

ki_query_active_all

Each record in ki_query_active_all represents the portion of a given query or REST endpoint call being run on a given worker rank at the time this catalog table was queried. It returns general information about the query portion running on the given worker rank. See ki_query_workers for worker-specific details.

ki_query_history

Each record in ki_query_history represents a single query or REST endpoint call made to the database. It will include all SQL queries, but not direct calls to DML-related endpoints, like:

ki_query_span_metrics_all

Each record in ki_query_span_metrics_all represents an independent operation that was processed on a given rank in order to fulfill a given query request, along with the statistics collected for that operation. This table will have one entry for each rank involved in processing a given operation and the statistics collected for that rank, per step of the SQL executed.

ki_query_workers

Each record in ki_query_workers represents the portion of a given query or REST endpoint call being run on a given worker rank at the time this catalog table was queried. It returns worker-specific information about the query portion running on the given worker rank. See ki_query_active_all for general query processing details.

ki_rag_embeddings

Each record in ki_rag_embeddings represents a table or sample definition of a SQL-GPT context and its associated embeddings.

ki_role_members

Each record in ki_role_members represents the mapping of a role to a user or role that is a member of that role.

ki_schema_registry

Each record in ki_schema_registry represents a schema encountered in a given subscription partition that single target table has through a single Kafka data source.

ki_schemas

Each record in ki_schemas represents a schema in the database.

ki_streams

Each record in ki_streams represents a single stream (table monitor).

ki_tiered_objects

Each record in ki_tiered_objects represents a single tiered object residing in a given tier on a given rank. A tiered object may occupy multiple tiers simultaneously, producing one record per object, tier, and rank combination. Tiered objects are not limited to table columns.

ki_users_and_roles

Each record in ki_users_and_roles represents either a user or role.