Page MenuHomePhabricator

Search should state (approximate) number of results for a query
Closed, DeclinedPublic

Description

As a user who performed a very "big" search in maniphest, I want to know how many pages there may be after the first, or ideally the exact number of search results, either for statistics' sake or in order to plan my actions on the results accordingly.

Cf. https://phabricator.wikimedia.org/maniphest/query/rtD5OXOlaUbe/#R which probably has tens of thousands results, or maybe thousands, but I have no idea.

Event Timeline

Nemo_bis created this task.Nov 25 2014, 7:59 AM
Nemo_bis raised the priority of this task from to Needs Triage.
Nemo_bis updated the task description. (Show Details)
Nemo_bis changed Security from none to None.
Nemo_bis added a project: Phabricator.
Nemo_bis added a subscriber: Nemo_bis.
Qgil triaged this task as Lowest priority.Nov 25 2014, 10:07 AM
Qgil edited projects, added Phabricator (Upstream); removed Phabricator.
Restricted Application added a subscriber: TerraCodes. · View Herald TranscriptMay 23 2016, 6:05 PM
epriestley added a subscriber: epriestley.

Because the visibility of each result depends on policies that can only be evaluated in the application, providing an exact count is very expensive, and providing an approximate count may disclose sensitive information. See https://secure.phabricator.com/T13133 for some more discussion of pagination and "overheating" (when queries fail early after filtering too many results).

Although it would be nice to provide an exact or approximate count, I don't see a way to do it without making most queries query dramatically more expensive, or sometimes disclosing information the viewer does not have permission to access, so I don't currently anticipate ever providing this functionality in the upstream.

Aklapper closed this task as Declined.May 22 2019, 1:12 PM
Aklapper added a subscriber: Aklapper.

Thanks for the detailed explanation!
Declining this task as the costs (given the architecture) seem to outweigh the benefits and as we don't plan to write/maintain downstream code changes either.