The CombiningRollupStrategy, used to produce/roll snapshots during the hourly tally, is currently loading all finest granularity snapshots in the supplied range when it does not need to. If the date of either of the snapshots does not match a date in the incoming calculations, the snapshot is just ingored during update, and was looked up for no reason at all.

It should only need to load any that match the dates of the incoming usage calculations.

For example, if an hourly tally run finds an un-tallied event well into the past and one that is current, the strategy will load all finest granularity snapshots within the range created by the two events, and would only end up updating 2 of them (1 per event).

DONE:

• Hourly tally no longer specifies a range when producing snapshots. Only pull snapshots for the hours applicable based on the incoming account usage calculations
• There are no changes to the REST APIs
• Hourly & nightly snapshots are validated
• Update CombiningRollupStrategy to use the incoming calculation dates to determine which finest granularity snapshots should be queried