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.

LMV_COLUMNSTORE_ACTIVE_MERGE_PLANS

This view contains information about merge plans that are running on the current node.

Column Name

Description

DATABASE_NAME

The name of the database.

TABLE_NAME

The name of the table.

PARTITION_ID

The ID of the related partition.

CREATION_TIME

The timestamp when the merge plan was created.

ACCESS_TIME

The timestamp when the information for this plan was collected.

LWPID

The process ID (PID) of the merge plan.

DETAILS_STATIC

A JSON string that provides details about merge plans that are running on the current node. Contains information relevant to the plan that will not change during the plan's execution. This field is provided for debugging purposes.

DETAILS_DYNAMIC

A JSON string that provides details about merge plans that are running on the current node. Contains information that may change during the plan's execution. For example, as a plan progresses and creates more segments, the IDs for those new segments will show up in this field. This field is provided for debugging purposes.

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