Collective attributes do not merged values with multi-valued attr

[JDanielA]

Describe the bug

Collective attributes (virtual attributes) are not merged, only the attributes from the first entry are returned. This bug report was inspired in a very similar problem detected in the non-community version of OpenDJ.

To Reproduce

You must to create two CollectiveAttributeSubentry with the same collective attribute "myattr" and two differents values.

E.g.

dn: cn=collective1,dc=example,dc=com
objectClass: top
objectClass: subentry
objectClass: collectiveAttributeSubentry
objectClass: extensibleObject
cn: collective1
myattr;collective: collective1
subtreeSpecification: {base "ou=people", specificationFilter "(uid=*)" }

dn: cn=collective2,dc=example,dc=com
objectClass: top
objectClass: subentry
objectClass: collectiveAttributeSubentry
objectClass: extensibleObject
cn: collective2
myattr;collective: collective2
subtreeSpecification: {base "ou=people", specificationFilter "(uid=user*)" }

Expected behavior

According to RFC 3671:

When an entry belongs to multiple entry collections, the entry's
   values of each collective attribute are combined such that
   independent sources of these values are not manifested to clients.
...
Collective attributes SHALL NOT be SINGLE-VALUED.

bin/ldapsearch --port 1389  -b "ou=people,dc=example,dc=com" -s sub "(uid=user.0)" myattr
dn: uid=user.0,ou=People,dc=example,dc=com
myattr: collective1
myattr: collective2

=> So it sounds like collective attribute values should be merged. Virtuals with other virtuals and reals values.

Current behavior

• "uid=user.0,ou=people,dc=example,dc=com" only has the first collective attribute value "myattr: collective1".
• If collectiveConflictBehavior is set to "merge-real-and-virtual" for both "cn=collective1" and "cn=collective2" AND if uid=user.0 has a real attribute "myattr", then only the real attribute values are returned for uid=user.0.

Version

• Version [OpenDJ 4.4.11]

[vharseko]

fixed 4.7.0