Sign inTry Free

PIPELINES_ICEBERG_FILES

Note

This is a Preview feature. The table schema is subject to change.

This view stores information about Iceberg data files ingested using pipelines with FORMAT ICEBERG.

Files listed in this view include current and previously processed snapshots.

This view is a subset of the PIPELINES_FILES information schema view that contains Iceberg-specific file status.

Column Name

Description

DATABASE_NAME

The name of the database associated with the file.

PIPELINE_NAME

The name of the pipeline associated with the file.

FILE_ID

Internal metadata file ID.

FILE_PATH

Storage location of the file as specified in the Iceberg metadata.

STATUS

Shows the state of the file. Possible values:

  • Data Unloaded This file has not been ingested yet.

  • Data Loaded This file has been ingested.

  • Pending Data Removal This file has been removed from the source Iceberg snapshot, but has not been removed from the destination SingleStore table.

  • Data Removed This file has been removed from the source Iceberg snapshot and the destination SingleStore table.

  • Positional Deletes Unloaded This file is a positional delete file that has not been applied to the destination SingleStore table yet.

  • Positional Deletes Loaded This file is a positional delete file that has been applied to the destination SingleStore table.

  • Equality Deletes Unloaded This file is an equality delete file that has not been applied to the destination SingleStore table yet.

  • Equality Deletes Loaded This file is an equality delete file that has been applied to the destination SingleStore table.

  • Pending Deletes Removal This is a delete file that has been removed from the source Iceberg snapshot, but has not been removed from the destination SingleStore table yet.

  • Deletes Removed This is a delete file that has been removed from the source Iceberg snapshot and the destination SingleStore table.

Last modified: July 15, 2025

Was this article helpful?

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