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.

SET AGGREGATOR

On this page

The SET AGGREGATOR command sets a sync variable to propagate to all aggregators in the cluster.

Syntax

SET AGGREGATOR variable_name = value

Arguments

  • variable_name: name of the sync variable.

  • value: value to be assigned to the sync variable.

Remarks

  • variable_name must be a variable type that can sync to all aggregators or a variable that can sync to all nodes (aggregators and leaves).

  • You cannot run this command on a non-sync variable.

  • This command must be run on the master aggregator.

Examples

Example 1

The following example syncs the variable auto_attach to all aggregators. SET AGGREGATOR can be run on auto_attach because auto_attach is a variable that can sync to all aggregators. This is indicated in the last sentence of the Description column for the variable.

SET AGGREGATOR auto_attach = 1;

Retrieve the variable’s value:

SELECT @@auto_attach;
+---------------+
| @@auto_attach |
+---------------+
|             1 |
+---------------+

Example 2

The following example syncs the variable regexp_format to all aggregators. SET AGGREGATOR can be run using regexp_format because regexp_format is a variable that can sync to all nodes (leaves and aggregators). This is indicated in the last sentence of the Description column for the variable.

SET AGGREGATOR regexp_format = "extended";

Retrieve the variable’s value:

SELECT @@regexp_format;
+-----------------+
| @@regexp_format |
+-----------------+
| extended        |
+-----------------+

Related Topics

Last modified:

Was this article helpful?

On this page

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