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_COLLECTED_ROW_CHANGE_COUNTS

This view displays the best-effort counter for the number of changes that have been observed for the table partitions over time, and are persisted to disk.

More specifically, this view contains the number of row changes (inserts, updates, and deletes) that have been applied to the table as a destination.

The write behavior to the view is controlled via the following engine variables: change_count_write_interval and background_statistics_collection_interval

Column name

Description

table_name

The name of the table.

database_name

The name of the database containing the table.

partition

The ID of the partition.

total_changes

The total cumulative number of rows changed for this table on this partition.

last_analyzed_total_changes

The last recorded change count, when the statistics collection was triggered based on the metadata.

An example query related to this view:

SELECT table_name, database_name, SUM(TOTAL_CHANGES), SUM(LAST_ANALYZED_TOTAL_CHANGES) FROM MV_COLLECTED_ROW_CHANGE_COUNTS;
+------------+---------------+---------------------+----------------------------------+
| table_name | database_name | sum (TOTAL_CHANGES) | sum(LAST_ANALYZED_TOTAL_CHANGES) |
+------------+---------------+---------------------+----------------------------------+
| t          | db1           |                   8 |                                8 |
+------------+---------------+---------------------+----------------------------------+

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