Learn more about these different git repos.
Other Git URLs
At the moment, sssd indexes objectclass, which is wasteful, because it creates a single huge index with all objects in there.
Instead, we should not index objectclass and let users and groups use objectlass and also let other object types use objectcategory instead which will be indexed.
Metadata Update from @jhrozek: - Issue assigned to sbose - Issue priority set to: critical - Issue set to the milestone: SSSD 1.16.0 - Issue tagged with: PR, RFE, performance
Metadata Update from @jhrozek: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1482555
Issue linked to Bugzilla: Bug 1482555
Since we are required to release a new upstream tarball no later than Friday Oct-20, I'm moving tickets that will not be closed by that date to the next milestone, 1.16.1
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.16.1 (was: SSSD 1.16.0)
Metadata Update from @jhrozek: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1482555, https://bugzilla.redhat.com/show_bug.cgi?id=1373547 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1482555)
Issue linked to Bugzilla: Bug 1373547
I created
https://github.com/SSSD/sssd/pull/450
for this. In contrast to the title the patches go the other way round and replace objectClass in user and group objects with a different attribute which is not indexed.
Metadata Update from @sbose: - Custom field patch adjusted to on
master:
Metadata Update from @jhrozek: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
And fixing a warning.
Additional patch
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/4529
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.
Login to comment on this ticket.