Sign inTry Free

Important

Self-managed SingleStore will soon transition from version 9.1 RC to version 10. This new semantic versioning scheme will provide SingleStore with finer control over engine and feature releases that were not possible with the current versioning scheme.

In the interim, SingleStore 9.1 RC can be used to preview, evaluate, and provide feedback on the new and upcoming features in SingleStore 10 prior to its general availability. Ahead of this transition, SingleStore 9.0 is recommended for production workloads, which can later be upgraded to SingleStore 10.

MV_AGGREGATED_COLUMN_USAGE

This view provides a summary of mv_query_column_usage, aggregating over the columns over all queries run.

Column name

Description

database_name

The name of the database, or NULL if none could be assigned.

table_name

The name of the table to which the column belongs.

column_name

The aggregated column information is displayed for this column.

equijoins

The number of equijoins this column has been involved in over all queries run over the table.

inequality_joins

The number of inequality joins this column has been involved in over all queries run over the table.

equality_preds

The number of equality predicates in the WHERE or ON clause this column has been involved in all queries run on the table.

inequality_preds

The number of inequality predicates in the WHERE or ON clause this column has been involved in all queries run on the table.

groupbys

The number of GROUP BY clause in the column involved in all queries run on the table.

reshuffles

The number of reshuffle key in the column, involved in all queries run on the table.

orderbys

The number of ORDER BY clause in the column involved in all queries run on the table.

outputs

The number of times the column was returned as the result of a query.

query_appearances

The number of distinct queries the column appears in all queries run on the table, which is equivalent to the number of times the column appears in the first table.

Last modified:

Was this article helpful?

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In