Important

Helios features are now enabled during weekly update windows and are no longer directly tied to SingleStore engine releases. Refer to the release notes to view the latest features available in your Helios cluster.

CROSS_QUERY_STATS_CACHE

This view contains metadata about cross query stats cache entries for the connected aggregator.

Example:

SQL

SELECT * FROM information_schema.cross_query_stats_cache;

| HASH                | ROWCOUNT_INITIALIZED | ROWCOUNT | LAST_HIT_TIME | LAST_UPDATE_TIME | ADDED_TIME | HIT_COUNT | QUERY_TEXT                                          |
|---------------------|----------------------|----------|---------------|------------------|------------|-----------|-----------------------------------------------------|
| -128073634921048162 | 1                    | 10       | 677           | 677              | 657        | 17        | SELECT COUNT(*) FROM 'xx' /*sampling_query*/ ...    |

Column Name	Description
`HASH`	64‑bit hash of the query or subquery shape used as the cache key; matches the `fr_track_hash` seen in query profiles. Queries are hashed to integer values in order to look up associated rowcounts.
`ROWCOUNT_INITIALIZED`	Boolean flag indicating whether the entry has a rowcount associated with it. This may be false if the entry is tied to a sampling query that has not yet finished.
`ROWCOUNT`	Rowcount associated with the entry.
`LAST_HIT_TIME`	The last time the entry was used, either by reading from it or writing to it. The time is based on the number of ticks since the server started up. There is no conversion to a Unix timestamp.
`LAST_UPDATE_TIME`	The last time the entry was written to. The time is based on the number of ticks since the server started up. There is no conversion to a Unix timestamp.
`ADDED_TIME`	The time the entry was created. The time is based on the number of ticks since the server started up. There is no conversion to a Unix timestamp.
`HIT_COUNT`	Total number of times the entry has been written to and read from once rowcounts have been initialized.
`QUERY_TEXT`	This column is empty by default to save memory. Once `enable_cross_query_stats_store_query_text` is enabled, the query text associated with the entry is displayed. Currently works for sampling queries only.

All time columns use a tick count from server startup rather than Unix timestamps.

CROSS_QUERY_STATS_CACHE

Was this article helpful?

Was this article helpful?