I’m trying to better understand the use case for the @count index in Dgraph. From what I gather, it’s only necessary when we need to filter or sort nodes based on the number of values they have for a specific predicate — for example, how many friends a node has. In that case, we’d write something l…

That’s correct. Note that the @count directive would also be needed for “root functions” that use count, e.g.: user(func:eq(count(friend),4)) { name } In your second example, the set of UIDs is already collected in the search so no @count predicate is required.

When is the @count index actually needed in Dgraph?

Users Dgraph

system (system) Closed May 12, 2025, 6:43am 3

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Tracking zero counts Dgraph	15	1128	September 3, 2020
[GitHub] Tracking zero counts Dgraph dgraph , status:accepted , area:querylang , priority:p3 , area:indexes	2	599	April 21, 2020
Count Queries in GraphQL GraphQL rfc , area:graphql	22	20515	March 19, 2021
Suggest more quickly count predicate total number Dgraph	2	960	January 9, 2019
Add @count to GraphQL schemas and queries Dgraph dgraph , kind:feature , area:graphql	3	1672	July 4, 2020

When is the @count index actually needed in Dgraph?

Related topics