Sorry. I did not answer your db2index question. I have two servers
using multimaster replication and I did run db2index.pl on both servers
after adding the index.
As to Ludwig's suggestion, I can run the queries using ":caseIgnoreIA5Match:"
in an extensible match search filter (memberuid:caseIgnoreIA5Match:=c00001096)
and the results are correct. I did not perform any timing tests on that before
I created the index so I cannot say if it is faster after the index was created.
My feel is that it is faster.
I will check the memberuid.db file.
I would not be surprised if, as Ludwig states, the default matching rule for
the attribute is used unless it is overridden in the search filter. That was
just not my understanding going in.
Thanks for your time so far.
--
using multimaster replication and I did run db2index.pl on both servers
after adding the index.
As to Ludwig's suggestion, I can run the queries using ":caseIgnoreIA5Match:"
in an extensible match search filter (memberuid:caseIgnoreIA5Match:=c00001096)
and the results are correct. I did not perform any timing tests on that before
I created the index so I cannot say if it is faster after the index was created.
My feel is that it is faster.
I will check the memberuid.db file.
I would not be surprised if, as Ludwig states, the default matching rule for
the attribute is used unless it is overridden in the search filter. That was
just not my understanding going in.
Thanks for your time so far.
From: "William Brown" <william@xxxxxxxxxxxxxxxx>
To: "General discussion list for the 389 Directory server project." <389-users@xxxxxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, August 9, 2018 6:07:17 PM
Subject: [389-users] Re: Attempting to make memberUID searches case insensitive
On Thu, 2018-08-09 at 08:23 -0500, Patrick Landry wrote:
> So what is the point of adding the matching rule when defining the
> index? Is that
> simply so that the index is built with the *capability* of supporting
> searches using
> that matching rule explicitly?
I think it would be worth trying Ludwig's suggestion so we can work out
*what's* going on. Perhaps the assumption we are making about what the
MR does is incorrect, and it's building a supplemental index. It's good
to check these things to understand the behaviours.
Perhaps something else to do is check to see what content is in the
memberuid.db file to see what indexes were added.
Finally, did you run db2index again? I don't know if you answered this.
--
Sincerely,
William
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx/message/WZZPSVL7QQWQSR43BHTJ6NTPVESYPZ2N/
--
_______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx/message/74R5TUTPOHGEDSHQQKYJ356NAPYLTEYC/
