Mods to handle generation of min/max aggregations in-memory.  It will at...

...tempt to read the relevant aggregation bin from Cassandra once (during a startup situation, etc) and all other agg state is handled in memory.
Addressed with new test.

On 9/11/14 1:04 PM, Jon Dugan wrote:
> In esmond/cassandra.py:
>
>> +        memory leaks.
>> +        """
>> +
>> +        ret = None
>> +
>> +        if not self.aggregation_cache.get(agg.get_key(), None):
>> +            self.aggregation_cache[agg.get_key()] = dict()
>> +            # there is no row key for this aggregation so to
>> +            # an initial lookup to see if this is a restart and seed
>> +            # the cache from the currently requested aggregation.
>> +            # this read will only happen once per aggregation row
>> +            # after startup or when seeing a new interface, etc.
>> +            try:
>> +                lookup = self.stat_agg._column_family.get(agg.get_key(),
>> +                            super_column=agg.ts_to_jstime())
>> +                self.aggregation_cache[agg.get_key()][agg.ts_to_jstime()] = dict(lookup)
>
> According to the coverage report this line isn't tested.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/esnet/esmond/pull/28/files#r17445124>.
>