Description of problem:
I define an index with: nssubstrbegin: 2
like this: dn: cn=uid,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config objectClass: top objectClass: nsIndex objectClass: extensibleObject cn: uid nsSystemIndex: false nsIndexType: eq nsIndexType: pres nsIndexType: sub nssubstrbegin: 2 nssubstrmiddle: 2 nssubstrend: 2
And a query with filter (uid=n*) seems not to be using the index:
[25/Feb/2015:15:37:06 +0100] conn=7 op=1 SRCH base="o=redhat" scope=2 filter="(uid=n*)" attrs=ALL [25/Feb/2015:15:37:06 +0100] conn=7 op=1 RESULT err=0 tag=101 nentries=1 etime=0 notes=A
git patch file (master) 0001-Ticket-48109-substring-index-with-nssubstrbegin-1-is.patch
git patch file (master) -- CI test 0002-Ticket-48109-CI-test-added-test-cases-for-ticket-481.patch
Reviewed by Rich (Thank you!!)
Pushed to master: 8f1eef1..71f7659 master -> master commit 71f7659 commit ae69e4a
Pushed to 389-ds-base-1.3.3: a875da1..09fc02e 389-ds-base-1.3.3 -> 389-ds-base-1.3.3 commit 09fc02e commit 511ec03
Fixed a compiler warning reported by Jenkins (#514)
71f7659..3701875 master -> master commit 3701875
09fc02e..d6f7b97 389-ds-base-1.3.3 -> 389-ds-base-1.3.3 commit d6f7b97
git patch file (master) -- fixing a regression 0001-Ticket-48109-substring-index-with-nssubstrbegin-1-is.2.patch
Pushed to master: bb0d222..2eba67c master -> master commit 2eba67c
Pushed to 1.3.3: 1fe0088..650ca94 389-ds-base-1.3.3 -> 389-ds-base-1.3.3 commit 650ca94
git patch file (master) -- stop logging a bogus error messages 0001-Ticket-48109-substring-index-with-nssubstrbegin-1-is.3.patch
Reviewed by Mark (Thank you!!)
Pushed to master: cb22bb3..230ace2 master -> master commit 230ace2
Pushed to 389-ds-base-1.3.4: 7715ac1..e001de5 389-ds-base-1.3.4 -> 389-ds-base-1.3.4 commit e001de5
Metadata Update from @nhosoi: - Issue assigned to nhosoi - Issue set to the milestone: 1.3.3.9
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/1440
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.