Repository navigation

fix: Ensure that prod/dev interval and physical model logic consistently uses Deployability - #5988

Closed

davem-bis wants to merge 8 commits into

SQLMesh:mainfrom

davem-bis:feature/DRM/resolve-indirect-non-breaking-deployable-representative-mismatch

Closed

fix: Ensure that prod/dev interval and physical model logic consistently uses Deployability#5988
davem-bis wants to merge 8 commits into
SQLMesh:mainfrom
davem-bis:feature/DRM/resolve-indirect-non-breaking-deployable-representative-mismatch

Commits on Aug 20, 2026
- Updated representativeness for indirect_non_breaking models to match deployability.
  davem-bis
  committed
  27cbee2
- Updated test objects names to be more descriptive.
  davem-bis
  committed
  95f9af2
Commits on Aug 25, 2026
- Merge remote-tracking branch 'origin/main' into feature/DRM/resolve-indirect-non-breaking-deployable-representative-mismatch
  davem-bis
  committed
  d91bc18
Commits on Aug 26, 2026
- Switched missing_interval and physical model logic to use deployability instead of representativeness for determining whether dev or prod instance of each should be used.
  davem-bis
  committed
  b0443a6
- Reverted representativeness logic to before based on testing.
  davem-bis
  committed
  a74d550
Commits on Sep 2, 2026
- Merge branch 'SQLMesh:main' into feature/DRM/resolve-indirect-non-breaking-deployable-representative-mismatch
  davem-bis
  authored
  97bfc28
- Updated is_representative docstring, and changed the physical table mapping to use the deployability index.
  davem-bis
  committed
  8b45e3f
Commits on Sep 14, 2026
- Merge branch 'SQLMesh:main' into feature/DRM/resolve-indirect-non-breaking-deployable-representative-mismatch
  davem-bis
  authored
  163b85b