Currently for any datum query where None < aggregation < Hour then a total result count will never be returned. This was done because calculating aggregate results for levels < Hour is expensive and slow. Requesting a total count means the server must execute the query twice: once for the total count, and then once for the requested page. This breaks client apps that use the DatumLoader JavaScript class in parallel query mode, as it depends on getting a total result count in order to make parallel requests for subsequent pages of results.

This ticket is for allowing the total result count to be returned. We now have the withoutTotalResultsCount query parameter so clients have the option to disable this if they want to.