I have created a JIRA ticket for this issue:
https://issues.apache.org/jira/browse/DIRAPI-340
Incidentally, I also have a fix that I'm going to test and apply asap.
(the fix is pretty straightforward)
On 30/04/2019 16:29, Sergey Mikhno wrote:
Thank you again,
Is it possible to get a fix
Dear Emmanuel,
I spent now more than a week trying to understand why uniqueMember index
doesn't work and still have no progress in understanding the problem.
With a defined index on uniqueMember my query brings empty result
*(**&*
*(*objectclass*=*groupOfUniqueNames*)*
*(**|*
Hi Sergey,
I can positively confirm that there is a problem. I'm able to reproduce
the issue you are facing in a unit test.
I'm currently debugging the server, and hope to come with a quick answer
(and hopefully a fix).
On 30/04/2019 11:33, Sergey Mikhno wrote:
Dear Emmanuel,
I spent
Ok, this a clear bug. The UniqueMemberComparator.compare() method is
badly implemented, and returns either 0 or -1, which means we can't
browse the index, as we never get a +1 (ie, provided uniqueMember is
superior to the stored one).
I'll get that fixed.
On 30/04/2019 15:59, Emmanuel
Hi Emmanuel,
Thank you very much for your quick response,
Please let me know if you need more information.
Best regards
Sergey Mikhno
Software Developer
Galexis AG
On Tue, Apr 30, 2019 at 3:59 PM Emmanuel Lécharny
wrote:
> Hi Sergey,
>
>
> I can positively confirm that there is a problem.
Thank you again,
Is it possible to get a fix for this issue, how should we go about it?
It would be great to be able to test a bugfix in our environment.
Best Regards
Sergey
On Tue, Apr 30, 2019 at 4:24 PM Emmanuel Lécharny
wrote:
> Ok, this a clear bug. The UniqueMemberComparator.compare()
