[OPENDJ-7068] Provide easy way to determine indexes needed by Rest2ldap queries Created: 02/Apr/20  Updated: 02/Apr/20

Status: Dev backlog
Project: OpenDJ
Component/s: ease of use, rest
Affects Version/s: 7.0.0
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Mark Craig Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:


Rest2ldap is being extended with cool features like recursive references and reverse references.

As the set of LDAP searches that Rest2ldap generates to respond to an HTTP request gets larger and less obvious from the pure REST view of the operations, it would be nice to be able to see why searches go unindexed, and give the directory administrator information that allows them to add the necessary indexes.

Today it's possible to disable suppression of access log messages for internal operations, and then try to repeat the LDAP searches with debugsearchindex to determine what might be missing. But it's not easy to do.

Comment by Mark Craig [ 02/Apr/20 ]

Perhaps we could provide something like a _debugsearchindex CREST action to facilitate the work?

The idea of this RFE arose from a discussion in a docs PR, https://stash.forgerock.org/projects/OPENDJ/repos/opendj-docs/pull-requests/1348/overview?commentId=924684.

Comment by Matthew Swift [ 02/Apr/20 ]

Thanks for raising this Mark. We're discussing similar functionality to this as part of IAM-2, although we haven't created any stories yet until the requirements are better understood.

One idea is to have an API call Rest2Ldap for making required configuration changes to DJ, including updating the schema and indexes. There's a few devils in the details though. For example, it is not possible to determine attribute syntaxes and matching rules from the Rest2Ldap configuration today, nor flag which fields are "searchable" or how. IDM has similar limitations.

Generated at Thu Feb 25 16:34:21 UTC 2021 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.