You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Mark Hanson (Jira)" <ji...@apache.org> on 2019/12/30 18:52:07 UTC
[jira] [Closed] (GEODE-7150) Use LONG instead of INT in Aggregation
Functions
[ https://issues.apache.org/jira/browse/GEODE-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Hanson closed GEODE-7150.
------------------------------
Transition from Resolved to Closed for Apache Geode 1.11.0 RC4 release.
> Use LONG instead of INT in Aggregation Functions
> ------------------------------------------------
>
> Key: GEODE-7150
> URL: https://issues.apache.org/jira/browse/GEODE-7150
> Project: Geode
> Issue Type: Improvement
> Components: querying
> Reporter: Juan Ramos
> Assignee: Juan Ramos
> Priority: Major
> Labels: GeodeCommons
> Fix For: 1.11.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> OQL aggregate functions ({{COUNT}} and {{AVG}}) can “silently” overflow as Geode internally uses {{int}} to compute the aggregations, basically meaning that we can return an overflowed value instead of the proper result.
> As an example, if {{COUNT}} evaluates to {{2147483648 (Integer.MAX_VALUE + 1)}} the user will receive {{-2147483648 (Integer.MIN_VALUE)}} and so on.
> We should modify the internal implementation to use `Long` instead of `Int`, and properly document the limitation (see GEODE-7146).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)