Dimension time ranges can be update after a fact was created which can lead to inconsistent data where the fact timestamp is not in the range of the dimension time range.
This already happened when we introduced the flex/plus nodes. And will now happen again with the automatic tenant updates.
Checklist
[x] Categorize the PR by setting a good title and adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog
Dimension time ranges can be update after a fact was created which can lead to inconsistent data where the fact timestamp is not in the range of the dimension time range.
This already happened when we introduced the
flex/plusnodes. And will now happen again with the automatic tenant updates.Checklist
bug,enhancement,documentation,change,breaking,dependencyas they show up in the changelog