Sign inTry Free

Important

New database features are no longer connected to engine versions; features are now enabled independently during scheduled update windows, and “major” and “minor” releases no longer exist in Helios. Please visit the release notes to view the latest features available in your database clusters.

MV_QUERY_COLUMN_USAGE

This view provides information about the usage of columns by queries in the workload.

Details about column that are used in joins, filters, group-bys, order-bys or reshuffles help to understand the frequency and cost of use of columns, and make better decisions about indexing and sharding of data.

Column name

Description

activity_name

The ID associated with the query. This will be the activity_name of all query tasks associated with the query.

database_name

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

table_name

The name of the table in the query.

column_name

The name of the column that exists in the table.

equijoins

The number of times this column was involved in an equijoin in the query.

non_equijoins

The number of times the column was involved in a non-equijoin in the query.

equality_preds

The number of times the column was involved in equality predicates in the WHERE or ON clause in the query.

inequality_preds

The number of times the column was involved in inequality predicates in the WHERE or ON clause in the query.

groupbys

The number of times the column was involved in a GROUP BY clause in the query.

orderbys

The number of times the column was involved in a ORDER BY clause in the query.

reshuffles

The number of times the column was member of reshuffle key in the query.

outputs

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

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