Skip to content

[FAQ] Bruin time_interval strategy fails on first run because table does not exist #210

@AsherJD-io

Description

@AsherJD-io

Course

data-engineering-zoomcamp

Question

Why does my Bruin asset using time_interval fail with a catalog error saying the table does not exist on first run?

Answer

When using the time_interval materialization strategy, Bruin executes a DELETE on the target table before inserting data for the requested time window.

On the first run, the table does not yet exist.
The DELETE statement fails and causes a catalog error.

To resolve this:

Run the asset once using create+replace to create the table.

Then switch the strategy back to time_interval.

Alternatively, run the pipeline with full refresh:

bruin run pipeline --full-refresh

This ensures the table exists before incremental logic runs.

Checklist

  • I have searched existing FAQs and this question is not already answered
  • The answer provides accurate, helpful information
  • I have included any relevant code examples or links

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions