Uploaded image for project: 'OpenDJ'
  1. OpenDJ
  2. OPENDJ-7714

Improve rest2ldap handling of searches implied by reverseReference type definitions

    XMLWordPrintable

    Details

    • Improvement
    • Status: Dev backlog
    • Blocker
    • Resolution: Unresolved
    • 7.1.0
    • None
    • common-repo, rest

      Description

      When the configuration of a REST endpoint has a property of type reverseReference, queries asking for that field will make rest2ldap search for all entries having the same attribute value as the entry passed as parameter.
      The search could translate very quickly in an unindexed search, as explained in OPENDJ-7685.
      In cases where the attribute is multi-valued , moreover, there will be as many searches issued as there are values, possibly all of them non indexed.

      To avoid evaluating all the searches over the entire backend, it would be nice, when possible, to use an OR filter with all the values, to get all entries at once.

      A related problem is also that such searches may encounter server limits (search or cursor limits), therefore they should be allowed to proceed regardless.

        Attachments

          Issue Links

            Activity

              People

              Unassigned Unassigned
              fabiop Fabio Pistolesi
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated: