The internal decision making process of how DS processes a query is often not understood well. As a result, when we see a complex query, and just give "notes=U", we don't really help people understand the issue. In addition certain queries while indexed, may still be poor in performance due to other issues.
After https://pagure.io/389-ds-base/issue/49290 is merged, we'll have enough inplace with idl_set to be able to provide a query plan explination. IE when do we shortcut, when do we fall back to filter tests, how many candidates remain etc. This will help improve application generated queries.
Metadata Update from @firstyear: - Issue assigned to firstyear
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 1.4 backlog
Metadata Update from @firstyear: - Issue set to the milestone: 1.3.7 backlog (was: 1.4 backlog)
Metadata Update from @firstyear: - Issue set to the milestone: 1.4 backlog (was: 1.3.7 backlog)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2376
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)