#3503 Do not index objectclass, add and index objectcategory instead
Closed: Fixed Opened by jhrozek.

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:

  • 2927da49dd8a16fff6312d89ad43cc355655800c
  • 98195e591c4d97caa6125e8214879660b740973f
  • 0e238c259c066cf997aaa940d33d6bda96c15925
  • 0cce3d3ad14caf406303cf2ce6bf80171b708a93

Metadata Update from @jhrozek:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

And fixing a warning.

master:

  • ab224783b581ebc77e475cd1377f4b5bcce52e9b

Additional patch

master:

  • 5b78fff78bb44d1af5420db23b02210f755f5f17

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.

Thank you for understanding. We apologize for all inconvenience.

Metadata