Rich Megginson wrote:
Please review and comment:
http://port389.org/wiki/Design/Fine_Grained_ID_List_Size
--
389-devel mailing list
389-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-devel
Hi Rich,
A nice design! It looks promising to solve the sticky problems.
Can I add a request -- a flag or something to the value to switch the
behaviour? E.g.,
nsIndexIDListScanLimit: maxsize[:indextype]/[:flags]/[:value[,value...]]
The flags could be KEYWORD_1|KEYWORD_2|... By default, no flags.
I only have one use case for now, but we may want to apply the scan
limit only when the specific filter is in AND, i.e.,
(&(objectclass=inetorgperson)(uid=UserA)), but not to the standalone
filter (objectclass=inetorgperson). This could be useful when DB stores
millions of inetorgperson's as well as millions of other objectclasses.
But not useful at all, if 99% of the entries are inetorgperson. So, for
example, the keyword could be ANDONLY...?
Thanks,
--noriko
--
389-devel mailing list
389-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-devel
