BIGINT aggregation issue in Hana rev 91

Question

Hi,
I have a BIGINT value field that isn't aggregating beyond 2147483648 (the max INTEGER value).
I'm seeing results as follows:
Period
Value
5
320,272,401
6
635,021,492
7
515,993,660
8
546,668,931
9
702,138,445
10
438,782,780
11
459,387,988
12
722,479,250
Result
-2,147,483,648
We've recently upgraded from rev 83 to 91. I'm pretty sure this is a new issue - has anyone else seen this?ect
I'm hoping there is some kind of fix as I don't want to have to convert fields throughout our system to a longer DECIMAL.
thanks
Guy

Answer 1

I've figured out this issue only affects Analytical Views that have calculated attributes.
Such views generate a CALCULATION SCENARIO in _SYS_BIC, which seems to incorrectly define my field (which is in the data foundation, modelled as a BIGINT) as SQL Type 4, sqlLength 9, as per the following:
{"__Attribute__": true,"name": "miles","role": 2,"datatype": {"__DataType__": true,"type": 66,"length": 18,"sqlType": 4,"sqlLength": 9},"kfAggregationType": 1,"attributeType": 0}
I also have calculated measures modelled as BIGINT's in the Analytical View. These are correctly defined in the CALCULATION SCENARIO with an SQL length of 18, for example:
{"__Attribute__": true,"name": "count","role": 2,"datatype": {"__DataType__": true,"type": 66,"length": 18,"sqlType": 34,"sqlLength": 18},"kfAggregationType": 1,"attributeType": 0}
This looks like a bug to me. As a work around I had to define a calculated measure BIGINT which simply equals my "miles" field. Then hide the original field.