Modifying model metadata often causes plan to fail if they haven't been run recently #4916
Description
- Create an INCREMENTAL_BY_UNIQUE_KEY model.
- Run sqlmesh plan.
- Wait a few days.
- Modify the model metadata in some way, for example add:
MODEL (
...
physical_properties ('mssql_merge_exists' = True)
)
- Run sqlmesh plan. It will fail:
---
+++
@@ -1,6 +1,7 @@
MODEL (
name [xxx].[xxx],
- dialect [tsql,normalization_strategy=case_sensitive]
+ dialect [tsql,normalization_strategy=case_sensitive],
+ physical_properties ('mssql_merge_exists' = 1)
)
SELECT
w.[ClientPrefix],
Directly Modified: xxx.xxx (Non-breaking)
Error: Start date / time (2025-07-06 00:00:00+00:00) can't be greater than end date / time (1751299200000)
I get this a lot when making changes to my templates. It forces me to run sqlmesh run to reprocess everything I have, before I can do a plan again. But as you can imagine this kind of model doesn't use timestamps/intervals and so I don't think this kind of logic check should apply.