Sign inTry Free

Important

Helios features are now enabled during weekly update windows and are no longer directly tied to SingleStore engine releases. Refer to the release notes to view the latest features available in your Helios cluster.

CLEAR PIPELINE ERRORS

On this page

Removes most pipeline errors.

This command is especially useful when a pipeline reaches its allocated storage space for errors, which causes the pipeline to pause. Errors stored in the active error file are still visible.

Syntax

CLEAR PIPELINE ERRORS [FOR <pipeline_name>]

Note

Specifying the name of a pipeline with CLEAR PIPELINE ERRORS is optional. When CLEAR PIPELINE ERRORS is run without specifying a pipeline, errors for all the pipelines are removed.

Argument

pipeline_name (Optional): Name of a pipeline.

Remarks

  • To increase the number of errors that can be stored, increase the value of the ingest_errors_max_disk_space_mb engine variable.

  • Query the information_schema.PIPELINES_ERRORS view to view the pipeline errors. For example:

    SELECT * FROM information_schema.PIPELINES_ERRORS;

Examples

CLEAR PIPELINE ERRORS;
START PIPELINE books;


CLEAR PIPELINE ERRORS FOR books;

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