DOWNLOAD STAGE FILE

Downloads a file at the specified path within a Stage.

Syntax

DOWNLOAD STAGE FILE '<stage_path>' 
    [ { IN GROUP { ID '<deployment_ID>' | '<deployment_name>' } | IN { ID '<deployment_ID>' | '<deployment_name>' } } ]
    [ TO '<local_path>' ]
    [ OVERWRITE ]
    [ ENCODING '<encoding>' ]

Arguments

  • stage_path: The path to the file in the Stage.

  • deployment_ID, deployment_name: The ID or name of the deployment (workspace group) in which the Stage is attached.

  • local_path: Specifies the download path in the local directory.

  • encoding: The encoding applied to the downloaded file.

Remarks

  • If the OVERWRITE clause is specified, any existing file with the same name at the specified download path is overwritten.

  • The IN and IN GROUP clauses specify the ID or the name of the deployment in which the Stage is attached.

  • By default, files are downloaded with the binary encoding. Specify the ENCODING clause and omit the TO clause, to view the contents of the file on the standard output.

  • If the TO <local_path> clause is not specified, the file is displayed on the standard output.

Examples

  • The following command displays the contents of a file in the Stage, on the standard output:

    DOWNLOAD STAGE FILE '/data/stats.csv'
    IN 's2wsg'
    ENCODING 'utf8';
  • The following command downloads the file to a specific location in the local storage:

    DOWNLOAD STAGE FILE '/data/stats.csv'
    IN 's2wsg'
    TO '/tmp/stats.csv'
    OVERWRITE
    ENCODING 'utf8';

    If the /tmp/stats.csv file exists in the local storage, it is overwritten.

Last modified: February 13, 2025

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