You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gearpump.apache.org by "Manu Zhang (JIRA)" <ji...@apache.org> on 2017/02/28 00:59:45 UTC
[jira] [Updated] (GEARPUMP-286) Different WindowAndGroups could end
up in one due to hashCode collision
[ https://issues.apache.org/jira/browse/GEARPUMP-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manu Zhang updated GEARPUMP-286:
--------------------------------
Description: Currently, we use a {{TreeMap}} to store and sort {{WindowAndGroup}}, which requires {{WindowAndGroup}} to be {{Comparable}}. However, {{Group}} is not and not supposed to be so I hacked with its {{hashCode}} for comparison. That is wrong since two {{Group}} could have identical {{hashCode}}. (was: Currently, we use a {{TreeMap}} to store and sort {{WindowAndGroup}}s, which requires {{WindowAndGroup}} to be {{Comparable}}. However, {{Group}} is not and not supposed to be so I hacked with its {{hashCode}} for comparison. That is wrong since two {{Group}}s could have identical {{hashCode}}s.)
> Different WindowAndGroups could end up in one due to hashCode collision
> ------------------------------------------------------------------------
>
> Key: GEARPUMP-286
> URL: https://issues.apache.org/jira/browse/GEARPUMP-286
> Project: Apache Gearpump
> Issue Type: Bug
> Components: streaming
> Affects Versions: 0.8.2
> Reporter: Manu Zhang
> Assignee: Manu Zhang
>
> Currently, we use a {{TreeMap}} to store and sort {{WindowAndGroup}}, which requires {{WindowAndGroup}} to be {{Comparable}}. However, {{Group}} is not and not supposed to be so I hacked with its {{hashCode}} for comparison. That is wrong since two {{Group}} could have identical {{hashCode}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)