List Duplicate Clusters
Open pairs of one tier, closed transitively into review decisions.
One tier per request, never mixed: an exact component and a strong one joined together would be a cluster nobody can act on, because half of it is safe to merge and half needs a person to look.
The closure is computed once and paged in memory. Unlike the pair queue it cannot be paged in SQL — a component is only known once every pair has been walked — so _CLUSTER_COUNT_MAX bounds it and the count says so.
Query parameters
Response
Successful Response
Changes
Changed in 1 of the 5 revisions of this API.2
- ○
added the optional property
//to the response with the statusresponse-optional-property-added
- ○
added the optional property
//to the response with the statusresponse-optional-property-added
This revision also has 8 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○