I see a problem running queries back to back.
Second query returns cells that are a sum of cells from the first query. Mondrian recognizes that fact and instead of retrieving data for the second query from the database it aggregates cells from the cache. During that roll up process the problem occurs.
I am having an issue when Mondrian rolls up data from cache. It seems to be happening here: SegmentBodyIterator. It looks like this is loaded from the cache: DenseDoubleSegmentBody, but the first value is zero so SegmentBodyIterator skips the first value and reports size() = (one less than in the cache). But index is not adjusted and as a result I am missing the last value from the cache in my total. Please let me know if this is not the right place to report this, but I just wanted to find out whether this is a problem or maybe I am missing something.
Second query returns cells that are a sum of cells from the first query. Mondrian recognizes that fact and instead of retrieving data for the second query from the database it aggregates cells from the cache. During that roll up process the problem occurs.
I am having an issue when Mondrian rolls up data from cache. It seems to be happening here: SegmentBodyIterator. It looks like this is loaded from the cache: DenseDoubleSegmentBody, but the first value is zero so SegmentBodyIterator skips the first value and reports size() = (one less than in the cache). But index is not adjusted and as a result I am missing the last value from the cache in my total. Please let me know if this is not the right place to report this, but I just wanted to find out whether this is a problem or maybe I am missing something.