Recreating an index for the same attribute but changing the case of for example 1 letter, results in abandoned indexfile
389-ds-base-1.4.4.3-20200615git4cfa3745e.fc31.x86_64
1. Create a user object with additional attributes: objectClass: mozillaabpersonalpha mozillaCustom1: xyz 2. Add an index entry mozillacustom1 3. Reindex the backend 4. Check the content of the index (after it has been flushed to disk) mozillacustom1.db 5. Remove the index 6. Notice the mozillacustom1.db is removed 7. Recreate the index but now use the exact case as mentioned in the schema 8. Reindex the backend 9. Notice the indexfile on disk still show all lowercase 10. Check that an ldapsearch return the results(mozillacustom1=xyz) 11. Restart the instance 12. Notice that an ldapsearch does not return a result(mozillacustom1=xyz) 13. Reindex the backend 14. Notice the second indexfile for this attribute 15. The all lowercase indexfile is abandoned and no longer updated.
The indexfile is created with the wrong name and a search using this index returns no results.
Recreating a index should result in a new indexfile as per the case specified and used accordingly, even after a restart.
Metadata Update from @spichugi: - Issue assigned to spichugi
Metadata Update from @spichugi: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1442386
Metadata Update from @mreynolds: - Issue priority set to: normal - Issue set to the milestone: 1.4.2
https://pagure.io/389-ds-base/pull-request/51168
fe48b60..526b542 master -> origin/master 3fdb2ed..8b7a1cd 389-ds-base-1.4.2 -> 389-ds-base-1.4.2 9e1a88c..58699ec 389-ds-base-1.4.3 -> 389-ds-base-1.4.3
Metadata Update from @spichugi: - 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/4210
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.