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_FTS_MERGED_INDEXES

This view shows full-text indexes that span multiple JLucene segments. The view only includes merged indexes, that is indexes with more than one segment.

Column Name

Description

DATABASE_NAME

The name of the database.

TABLE_NAME

The name of the table on which this index is built.

PARTITION

The ID of the partition where this index resides.

NODE_ID

The ID of the node where this index resides.

FTS_INDEX_ID

The internal ID of the full-text index.

NUM_SEGMENTS

The number of Lucene segments in this index.

This value is always greater than 1 as this view only includes merged indexes.

SEGMENT_IDS

A JSON array of the individual Lucene segment IDs that make up this index.

NUM_ROWS

The total number of rows indexed.

FTS_INDEX_VERSION

The full-text index metadata version.

SIZE

The uncompressed size of the full-text index, in bytes.

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