[DIRSERVER-1698] Search on entries with multiple AVA in RDN does not work crrectly if the initial RDN order is not used

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0-M5
• Fix Version/s: 2.0.0-M7
• Assignee: Unassigned
• Reporter: Emmanuel Lécharny
• Created: 22/Feb/12 12:23
• Updated: 19/May/19 10:13
• Resolved: 27/Feb/12 15:13

Description

If we create an entry using a RDN with multiple AVA, like this one :

dn: cn=Doe+gn=John, ou=system
ObjectClass: top
ObjectClass: person
cn: Doe
gn: John
sn: John Doe

then searching for the entry using its DN with cn=Doe+gn=John, ou=system as a base, you'll get the entry. However, doing the same search but with the base DN gn=John+cn=Doe, ou=system, you will get nothing.

This is due to the fact that the ParentIdAndRDN.compareTo() method use the String value of the RDN, so the ordering is dependent on the AVA position in the String.

This is bad. We must rewrite the CcompareTo method to compare the AVA one by one in the correct order.