TL;DR: clarify when models are only being backfilled because of the need for dev previews
SQLMesh provides an explanation of the actions a plan will take if the --explain flag is passed to the CLI command.
For plans against non-prod environment, the explanation notes when a backfill is a dev preview that will not be reused in prod. Example:
│ └── project__dev.the_table -> "db"."sqlmesh__theschema"."the_table__11617724__dev"
│ ├── Fully refresh table
│ │ └── preview: data will NOT be reused in production <------------------- PREVIEW NOTE
│ └── Run 'not_null' audit
If a plan includes indirect non-breaking changes, the user expects those models NOT to be backfilled. However, the backfill section header is:
This is confusing because those models should not "need" to be backfilled - they are only being backfilled because of the need to preview.
We should provide additional explanation to clarify this, possibly creating a separate section for Models needing previews.
TL;DR: clarify when models are only being backfilled because of the need for dev previews
SQLMesh provides an explanation of the actions a
planwill take if the--explainflag is passed to the CLI command.For plans against non-prod environment, the explanation notes when a backfill is a dev preview that will not be reused in prod. Example:
If a plan includes indirect non-breaking changes, the user expects those models NOT to be backfilled. However, the backfill section header is:
This is confusing because those models should not "need" to be backfilled - they are only being backfilled because of the need to preview.
We should provide additional explanation to clarify this, possibly creating a separate section for
Models needing previews.