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.

SHOW LINKS

On this page

The SHOW LINKS command shows all connection links on S3, Azure, GCS, HDFS, Kafka, or other data sources for a permitted user.

Syntax

SHOW LINKS [ON db_name]

Output

Column

Description

Link

Name of the connection link provided at the time of link creation

Type

Type of connection link - S3, Azure, GCS, HDFS, or Kafka

Description

Details of the connection link

Config

Connection link configuration (JSON)

Remarks

  • db_name is the name of the SingleStore database. It is an optional parameter. If not specified, the connection links in the current (context) database are displayed.

  • To view and use connection links, you need the SHOW LINK permission. Contact your database administrator to grant this permission.

  • See the Permission Matrix for the required permission.

Example

The following example displays the connection links to the Orderdb database:

SHOW LINKS ON Orderdb;
+-------------------+------+---------------------------------+------------------------+
| Link              | Type | Description                     | Config                 |
+-------------------+------+---------------------------------+------------------------+
| product_S3        | S3   | Products ordered in December    | {"region":"us-east-1"} |
+-------------------+------+---------------------------------+------------------------+

You can also query the information schema to view all links in the cluster, along with the link details.

SELECT * FROM INFORMATION_SCHEMA.LINKS;
+---------------+------------+------+------------------------------+-----------------------------+
| DATABASE_NAME | LINK       | TYPE | DESCRIPTION                  | CONFIG                      |
+---------------+------------+------+------------------------------+-----------------------------+
| Orderdb       | product_S3 | S3   | Products ordered in December | {"region":"us-east-1"}      |
+---------------+------------+------+------------------------------+-----------------------------+

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