# PIPELINES\_CURSORS This view contains information about a pipeline’s offset ranges. Each row represents a single data source partition. ## information\_schema.PIPELINES\_CURSORS Schema | Column Name | Description | | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `DATABASE_NAME` | The name of the database associated with the offsets. | | `PIPELINE_NAME` | The name of the pipeline associated with the offsets. | | `SOURCE_TYPE` | The name of the pipeline’s data source, such as`KAFKA`or`S3`. | | `SOURCE_PARTITION_ID` | The identifier for a data source’s partition from which offsets are extracted. For an S3 pipeline, this value represents the name of a bucket’s object. | | `EARLIEST_OFFSET` | The earliest offset for an offset range. This value indicates the starting offset and`LATEST_OFFSET`indicates the ending offset in an offset range. This value may be`NULL`if data extraction is still in progress or failed. | | `LATEST_OFFSET` | The bounding offset for an offset range, exclusive. This value indicates the ending offset and`EARLIEST_OFFSET`indicates the starting offset in an offset range. This value may be`NULL`if data extraction is still in progress or failed. | | `CURSOR_OFFSET` | The next offset at which the pipeline will start loading in this partition. This number represents the end of the range which has already been loaded by this pipeline, exclusive; all future considered offsets will be beyond this. | | `SUCCESSFUL_CURSOR_OFFSET` | The offset cursor position in this source partition up to which data has been successfully loaded. This value is exclusive, all offsets below it have been successfully loaded, and the offset itself has not yet been loaded.When the pipeline is idle and`SUCCESSFUL_CURSOR_OFFSET`is lower than`CURSOR_OFFSET`, the offsets in between were skipped. Offsets are skipped only when`pipelines_stop_on_error`is`OFF`or when you set offsets manually using`ALTER PIPELINE`. | | `UPDATED_UNIX_TIMESTAMP` | The last updated time for an offset range in Unix timestamp format. | | `EXTRA_FIELDS` | Some extractors output additional information when extracting data from the source. For S3 pipelines, you may encounter a value of`{"size":}`, where``represents the size of an object in the source bucket. | > **📝 Note**: `CURSOR_OFFSET` and `SUCCESSFUL_CURSOR_OFFSET` are exclusive boundaries. Each value represents the offset at which the next read or load begins. This is not an offset that has already been processed. *** Modified at: October 27, 2026 Source: [/db/v9.0/reference/information-schema-reference/data-ingest/pipelines-cursors/](https://docs.singlestore.com/db/v9.0/reference/information-schema-reference/data-ingest/pipelines-cursors/) (An index of the documentation is available at /llms.txt)