Description
Values are considered equivalent even if they are not:
2020-10-29 16:15:11,791 [MODEL] [pool-7-thread-5] TRACE (com.evolveum.midpoint.model.impl.lens.IvwoConsolidator): Consolidating value equivalence class (49 of 63): Equivalence class members: (1) id=50 subtype: [ x ] extension: recStatus: d uuser: ... metadata: (...) targetRef: (...) activation: effectiveStatus: ENABLED Plus origins: [] Zero origins: (1) ItemValueWithOrigin: itemValue: id=50 subtype: [ x ] extension: recStatus: d uuser: ... metadata: (...) targetRef: (...) activation: effectiveStatus: ENABLED mapping: ... construction: null Minus origins: (1) ItemValueWithOrigin: itemValue: id=50 subtype: [ x ] extension: recStatus: a metadata: (...) targetRef: (...) activation: effectiveStatus: ENABLED mapping: ... construction: null Presence in existing item: (1) id=50 subtype: [ x ] extension: recStatus: a metadata: (...) targetRef: (...) activation: effectiveStatus: ENABLED Presence in apriori plus: [] Presence in apriori minus: []
Note that the values have different content: recStatus is different (a vs d), uuser is different. But the PCVs fall into one equivalence class, which is wrong.
The problem lies most probably here:
We shouldn't automatically consider values with matching IDs to be equivalent.
Attachments
Issue Links
- relates to
-
MID-7243 Slow consolidation for large items
-
- Open
-