This rule detects views where no valid requires constraint solution exists:
-
View maps only to CDF built-in containers:
Since CDF containers cannot be modified, no requires can be added.
-
No valid solution:
This view is causing issues when optimizing requires constraints
for other views, due to its structure (mapping non-overlapping containers)
Why it matters
These views will have suboptimal query performance that cannot be fixed by
adding or removing requires constraints. The only solutions require restructuring:
- Add a view-specific container that requires all the other containers in the view
- Restructure the view to use different containers
Example
View MultipleEquipments maps only to containers Valve and InstrumentEquipment.
The optimal constraints are Valve → CogniteEquipment and InstrumentEquipment → CogniteEquipment
due to other views needing these constraints to optimize their query performance.
This means however, that neither Valve nor InstrumentEquipment can reach each other without
creating complex ingestion dependencies. The view needs a new container or restructuring.
Further reading
Last modified on February 27, 2026
