Aggregate scan is still run even when no categories are configured
Reported by Paul Jones | July 14th, 2011 @ 03:57 PM
When a pair is configured with no aggregatable categories (ie, empty or sets only), then the scan will query for aggregates, then immediately query for entities. This is double work, and shouldn't be done - instead, we should just query entities immediately.
Comments and changes to this ticket
-
Paul Jones July 14th, 2011 @ 04:03 PM
- State changed from “open” to “resolved”
- Assigned user changed from “Paul Jones” to “Ben Hood”
Ready for QA
-
Ben Hood July 14th, 2011 @ 04:08 PM
(from [0e7ec1cca6d30419afe6d1b2ae79d1d803812f26]) [#293] Don't scan for aggregates when we don't have any bucketing initially. https://github.com/lshift/diffa/commit/0e7ec1cca6d30419afe6d1b2ae79...
-
-
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
Ben Hood