DLM checks the wrong constraint for data availability
When a dataflow has 2 Live and PiT versions of data,
Then the DLM checks the data availability against the wrong content constraint and thus returns the wrong total number of observations.
Steps to reproduce
- upload data on a Live version of a dataflow
- upload a second set of data on a PiT version of the same dataflow
- It creates 2 content constraints: one
ValidFrom
and oneValidTo
(A or B) - When qyering in the DLM for the number of observations, it queries against the wrong constraints and thus returns the number of observations of the PiT version