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_COLUMNSTORE_MERGE_STATUS

This view stores information about the status of background_merger processes for columnstore tables.

Column Name

Description

DATABASE_NAME

The name of the related database.

TABLE_NAME

The name of the related table.

PARTITION_ID

The ID of the related partition.

MERGER

Specifies whether the given status is for slow, fast, manual, or index merging.

  • (Current Groups) is the current state of the segment groups regarding the sort key.

  • (Current Index Groups on <index name>) is the current state of the cross segment index blobs (for multi column indexes).

  • (Current Index Groups on Column <column name>) is the current state of the cross segment index blobs (for single column indexes, and columns part of a multi column index).

  • Fast Merger / Slow Merger are the two background merger processes.

  • Manual Merger indicates a user running the OPTIMIZE TABLE command.

STATE

For rows corresponding to the current state of a merge process:

  • Idle - not doing anything.

  • Waiting - waiting on another merger (mainly for manual OPTIMIZE commands).

  • Preparing - gathering information for merge.

  • Merging Segments

  • Compacting Segments

  • Merging Indexes

  • Compacting Indexes

  • Updating Statistics

  • Populating Altering-Encoding

For rows corresponding to the current state of the table (Current Groups, etc.):

  • NULL

  • Building - only for newly added indexes that are not yet populated.

PLAN

The size, in number of segments, or the rows being merged.

PROGRESS_PERCENT

Merge progress represented as a number between 0 and 100.

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