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_COLUMNSTORE_FILES

This view stores information about columnstore files.

Column Name

Description

DATABASE_NAME

The name of the related database.

TABLE_NAME

The name of the related table.

FILE_TYPE

The type of a given columnstore file. Possible values include:

  • AUTOSTATS - stats for the optimizer

  • FULLTEXT - full-text index

  • INVERTED_INDEX - secondary hash index

  • COLUMN - data for columns, may be encoded

  • COLUMN_GROUP - indicates the column group index blobs

Both COLUMN and INVERTED_INDEX objects can be stored inside one columnstore file. In these cases, FILE_TYPE shows the type of the first object in that file. To get detailed information for all columns and indexes in each file, use MV_COLUMNAR_SEGMENT_INDEX.

FILE

The name of a given columnstore file.

HOST

The hostname or IP address for the related leaf node.

PORT

The port number of the related leaf node.

NODE_ID

The ID of the related leaf node.

PARTITION

The ID of the related partition.

SIZE

The size, in bytes, of a given columnstore file.

CREATION_TIME

The timestamp when a given columnstore file was created.

LSN

Log sequence number of the related blob file.

TERM

The term of the database, used to uniquely identify which node was the master of a specific database.

CHECKSUM

The crc32c checksum of the file contents.

STORAGE_ID

Storage ID of the database.

COMPUTE_ID

ID of the current active compute session for the database.

BLOB_COMPUTE_ID

ID of the compute session that wrote the file. Can differ from COMPUTE_ID.

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