Sign inTry Free

Appendix

On this page

Note

This is a Preview feature.

Example Bash Script: Automate Ingest Setup and Full Extract via API

This example Bash script automates the full setup of the Ingest UI checklist using API calls. It sets up a source MySQL database connection and a destination SingleStore database hosted in Helios, selects a table from a sample MySQL database called classicmodels, configures a periodic schedule, adds a license key, and finally triggers a full extract.

Note: Modify source and destination database configuration, table names, schedule, and license key to suit your environment.

Example Python Script: Automate Ingest Setup and Full Extract via API

This example Python script automates the full setup of the Ingest UI checklist using API calls. It sets up a source MySQL database connection and a destination SingleStore database hosted in Helios, selects a table from a sample MySQL database called classicmodels, configures a periodic schedule, adds a license key, and finally triggers a full extract.

Note: Modify source and destination database configuration, tables, schedule, and license key to suit your environment.

Example Bash Script: Automate Sliced Data Transfer via XL Ingest APIs

This example Bash script automates sliced data transfer using XL Ingest APIs. It assumes that the source and destination database connections are already configured in Ingest. The script selects a table, configures it to skip the initial extract (schema-only transfer), triggers a full extract, applies a license key in XL Ingest, sets up table slices based on a column (orderNumber), and finally triggers a sliced data transfer.

Note: Modify table names, slice values, and license key to suit your environment.

Example Python Script: Automate Sliced Data Transfer via XL Ingest APIs

This example Python script automates sliced data transfer using XL Ingest APIs. It assumes that the source and destination database connections are already configured in Ingest. The script selects a table, configures it to skip the initial extract (schema-only transfer), triggers a full extract, applies a license key in XL Ingest, sets up table slices based on a column (orderNumber), and finally triggers a sliced data transfer.

Note: Modify table names, slice values, and license key to suit your environment.

Last modified: October 17, 2025

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