Currently, chaise is using the Reference.getAggregates API to fetch the total count displayed in the recordset pages. This API will internally use the ermrest's aggregate API to fetch the cnt_d of the shortestkey.
While this works in most cases, in a table with millions of rows and complicated facet structure, the generated request might result in a timeout. That's why previously we decided to disable the count in CFDE tables.
We should investigate if there's a special treatment that we can do for CFDE to switch to use a more performant and customized Query for this request.
Currently, chaise is using the
Reference.getAggregates
API to fetch the total count displayed in the recordset pages. This API will internally use the ermrest'saggregate
API to fetch thecnt_d
of the shortestkey.While this works in most cases, in a table with millions of rows and complicated facet structure, the generated request might result in a timeout. That's why previously we decided to disable the count in CFDE tables.
We should investigate if there's a special treatment that we can do for CFDE to switch to use a more performant and customized Query for this request.
@karlcz Can you please add more details?