AGGREGATOR_ID

Returns the unique ID (node_id) for the current aggregator.

When you do not know the specific aggregator you are connecting to, either because you are connecting via the DML endpoint in SingleStore Helios or in situations where a load balancer is used, the ID returned by AGGREGATOR_ID() can be combined with CONNECTION_ID() to provide a cluster-wide unique identifier for the active session.

Syntax

AGGREGATOR_ID()

Return Type

Integer.

Example

SELECT AGGREGATOR_ID();
+-----------------+
| AGGREGATOR_ID() |
+-----------------+
|               8 |
+-----------------+

Last modified: November 8, 2023

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