consolidation-at-read-time: errors like "GetAggregated called with unknown aggSpan 60" #64

Dieterbe · 2015-11-30T09:52:48Z

these happen when loading chunks from /tmp/nmt.gob and since then the aggregation rules have changed.
we don't dynamically update the aggregation rules after importing the data. this would be pretty tricky anyway (accommodating various subtle differences in automagic ways)
and the loading/saving approach has been deprecated anyway, see #56 so i don't think we should spend time fixing this.

instead we may want to just deprecate the whole chunk saving/loading.

Dieterbe added a commit that referenced this issue Dec 3, 2015

disable aggmetrics saving/loading for now. see #64

e60a5bb

Dieterbe self-assigned this Dec 4, 2015

Dieterbe closed this as completed in 4dbf5b3 Dec 4, 2015

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

consolidation-at-read-time: errors like "GetAggregated called with unknown aggSpan 60" #64

consolidation-at-read-time: errors like "GetAggregated called with unknown aggSpan 60" #64

Dieterbe commented Nov 30, 2015

consolidation-at-read-time: errors like "GetAggregated called with unknown aggSpan 60" #64

consolidation-at-read-time: errors like "GetAggregated called with unknown aggSpan 60" #64

Comments

Dieterbe commented Nov 30, 2015