Sign inTry Free

Important

The SingleStore 9.1 release candidate (RC) is available now. It will be promoted to general availability (GA) soon and at that time it will be renamed to SingleStore 10.

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, while SingleStore 9.0 is recommended for production workloads.

MV_COLUMNAR_SEGMENT_INDEX

This view stores information about indexes used to sort columnstore segments.

Column Name

Description

DATABASE_NAME

The name of the related database.

TABLE_NAME

The name of the related table.

INDEX_NAME

The name of a given columnstore segment’s index.

SEGMENT_ID

The ID of a given columnstore segment.

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.

ENCODING

The type of encoding for a given column.

UNCOMPRESSED_SIZE

The size, in bytes, of the column.

COMPRESSED_SIZE

The size, in bytes, of a given segment index. The "uncompressed size" of the index is the size of the data in the indexed column. Since the index stores extra indexing structures it is possible for the index size to be larger than the data in the indexed column.

CREATION_TIME

The timestamp when a given columnstore segment 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.

FILE_OFFSET

Specifies the offset in the file where a given segment is stored.

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