Catalog Metadata
Every table makes metadata about itself available through special virtual tables that you can query through Hydrolix's SQL API or query UI. These include catalogs of the files and directories that hold tables' data and indexes, and descriptions of the columns and time-intervals held by each table's constituent partitions.
Catalog⚓︎
A catalog virtual table contains one row for every partition used by its associated fluid table. The row's data include that partition's filesystem path, the span of time-series data it contains, and the amount of storage space it takes up.
Catalog columns⚓︎
In the following table, "this partition" means the particular partition of fluid table data that each catalog row describes.
| Name | Purpose |
|---|---|
| partition | This partition's filesystem path, relative to the table's cloud-storage location. |
| min_timestamp | The earliest timestamp of the contiguous time-series data held by this partition. |
| max_timestamp | The latest timestamp of the contiguous time-series data held by this partition. |
| manifest_size | The size of this partition's manifest file, in bytes. |
| data_size | The size of this partition's data file, in bytes. |
| index_size | The size of this partition's index file, in bytes. |
Query a table's catalog⚓︎
Query a table's catalog using the special view name .catalog.
Concatenate the table and view with # and enclose the combined table and view name inside backticks.
The sample queries demonstrate how to query the catalog of the cluster's table hydro.logs.
To view the total table size in bytes, use
Use catalog access to analyze effects of configuration changes, especially in the ingestion software. Hydrolix recommends new partitions are created between 1 GB and 3 GB in size. The merge system compacts partitions to reach optimal storage size of 2 GB and 4 GB per partition.
Visualize the distribution of partition sizes per day for the last ten days with this query.