Bug 1011539 - [RFE] idlistscanlimit per index/type/value
[RFE] idlistscanlimit per index/type/value
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base (Show other bugs)
Unspecified Unspecified
medium Severity unspecified
: rc
: ---
Assigned To: Rich Megginson
Sankar Ramalingam
: FutureFeature
Depends On: 1004876
  Show dependency treegraph
Reported: 2013-09-24 09:51 EDT by Rich Megginson
Modified: 2014-06-17 23:00 EDT (History)
2 users (show)

See Also:
Fixed In Version: 389-ds-base-
Doc Type: Enhancement
Doc Text:
Cause: Consequence: Fix: Result:
Story Points: ---
Clone Of: 1004876
Last Closed: 2014-06-13 06:37:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rich Megginson 2013-09-24 09:51:18 EDT
+++ This bug was initially created as a clone of Bug #1004876 +++

This bug is created as a clone of upstream ticket:

With very large databases, some queries go through a lot of work to build huge ID lists for filter components with many matching IDs.  For example, a search for (&(objectclass=inetorgperson)(uid=foo)) may build a huge idlist for objectclass=inetorgperson only to throw it away to intersect it with uid=foo.  In these cases, it would be useful to be able to tell the indexing code to use a different idlistscanlimit for certain indexes, or use no idlist at all.  In the above case, it would be useful to tell the indexing code to skip building an idlist for objectclass=inetorgperson, but still use the default idlistscanlimit for other objectclass searches (e.g. objectclass=groupOfNames).

This would also help in https://fedorahosted.org/389/ticket/47474 - if there are several million IDs for each of the objectclass= filter components, being able to skip id list generation for the objectclass values would make that query very fast.

We can't reuse nsslapd-idlistscanlimit, so perhaps a new attribute

dn: cn=attrname,cn=index,...
objectclass: nsIndex
nsIndexIDSize: NNNN[:type][:eqvalue:eqvalue:...]

Where NNNN is the max ID list size (or 0 for no list at all)
type is the type of index (sub, pres, eq)
eqvalue are for equality indexes - these are the values to which the max ID list size applies

So in the case of ticket/47474, something like

dn: cn=objectclass,...
objectclass: nsIndex
nsIndexType: eq
nsIndexIDSize: 0:eq:organizationalPerson:inetOrgPerson:organization:organizationalUnit:groupOf

Would effectively disable id list generation for the objectclass values listed.

Note that this will apply to _all_ queries for any of the objectclass values, not just their use in conjunction with this particular search filter.
Comment 1 Rich Megginson 2013-09-24 10:13:20 EDT
Upstream ticket:
Comment 2 Rich Megginson 2013-09-24 13:34:02 EDT
r8138 | rmeggins@REDHAT.COM | 2013-09-24 11:32:56 -0600 (Tue, 24 Sep 2013) | 9 lines

Tests for the new feature Fine Grained ID List Size
new file filterscanlimit.sh tests have many positive and
negative tests to test features and error handling
tests pass with valgrind reporting no errors
upstream ticket - https://fedorahosted.org/389/ticket/47504
Comment 3 Sankar Ramalingam 2013-09-25 03:00:31 EDT
As per comment #2, the test cases are already automated in filter test suite. Hence, marking the qe_test_coverage+ flag.
Comment 5 Sankar Ramalingam 2013-12-20 08:33:12 EST
Automated test cases in TET for filter test suites are PASSing. Hence, marking the bug as Verified.

Build tested - 389-ds-base-

Snippets from the acceptance test report

added /tet/tet/../data/DS/6.0/filter/en/fslindexconfig-errors.21.ldif
added /tet/tet/../data/DS/6.0/filter/en/fslindexconfig-errors.22.ldif
TestCase [fsl1] result-> [PASS]

TestCase [fsl1] result-> [PASS]
Test fsl2 - test various combinations of filters and idlistscanlimit
loaded index config from /tet/tet/../data/DS/6.0/filter/en/fslindexconfig.ldif
modifying entry cn=config

TestCase [fsl2] result-> [PASS]
Comment 6 Ludek Smid 2014-06-13 06:37:02 EDT
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.

Note You need to log in before you can comment on or make changes to this bug.