389-ds 1.3.5-13 A IA5Match attribute is case sensitive. It is possible to index it with IgnoreIA5Match using 'nsMatchingRule'.
The IgnoreIA5 index works as expected but it triggers a warning:
[25/Aug/2016:16:37:19.600890195 +0200] default_mr_indexer_create: warning - plugin [caseIgnoreIA5Match] does not handle caseExactIA5Match
attachment ticket48973_test.py
Metadata Update from @tbordaz: - Issue set to the milestone: 1.3.6 backlog
Metadata Update from @mreynolds: - Issue close_status updated to: None - Issue set to the milestone: 1.3.7 backlog (was: 1.3.6 backlog)
The problem occurs when an index entry (in the backend config "cn=<attr>,cn=index,cn=<be_name>,..") contains one or more nsMatchingRule values.
For each value, the server tries to retrieve a matching rule that can manage it. It exists two mechanisms (old and new) to register Matching rules. The code retrieves Matching rule first using the old registering mechanism then if no MR is retrieved it uses the new mechanism. The old mechanism logs a warning when it find a MR indexer that can not managed the searched MR.
This log should rather be a debug message because the order of MR plugin is random. I think this message used to be a debug one but land into warning because of recent changes in MR indexing.
Metadata Update from @tbordaz: - Custom field reviewstatus adjusted to None
<img alt="0001-Ticket-48973-Indexing-a-ExactIA5Match-attribute-with.patch" src="/389-ds-base/issue/raw/files/e9c88aa920e588d5fd279b2671c5824ae5366b2faf2cbf196eed4c73cc3058c4-0001-Ticket-48973-Indexing-a-ExactIA5Match-attribute-with.patch" />
Metadata Update from @tbordaz: - Custom field reviewstatus adjusted to review (was: None)
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to ack (was: review)
ack, this look good,
<img alt="0001-Ticket-48973-Indexing-a-ExactIA5Match-attribute-with.patch" src="/389-ds-base/issue/raw/files/11c331ba6facda8bdf1e26932c2aae37bf32dd3509e4cc20aba553150e041371-0001-Ticket-48973-Indexing-a-ExactIA5Match-attribute-with.patch" />
git push origin master
Counting objects: 10, done. Delta compression using up to 8 threads. Compressing objects: 100% (10/10), done. Writing objects: 100% (10/10), 4.00 KiB | 0 bytes/s, done. Total 10 (delta 7), reused 0 (delta 0) To ssh://git@pagure.io/389-ds-base.git e9ad5f5..1d158cd master -> master
Metadata Update from @tbordaz: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2032
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.