You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@parquet.apache.org by "Zoltan Ivanfi (JIRA)" <ji...@apache.org> on 2018/01/10 14:46:00 UTC

[jira] [Updated] (PARQUET-1191) Type.hashCode() takes originalType into account but Type.equals() does not

     [ https://issues.apache.org/jira/browse/PARQUET-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zoltan Ivanfi updated PARQUET-1191:
-----------------------------------
    Reporter: Gabor Szadovszky  (was: Zoltan Ivanfi)

> Type.hashCode() takes originalType into account but Type.equals() does not
> --------------------------------------------------------------------------
>
>                 Key: PARQUET-1191
>                 URL: https://issues.apache.org/jira/browse/PARQUET-1191
>             Project: Parquet
>          Issue Type: Bug
>            Reporter: Gabor Szadovszky
>
> If two Type instances are equal according to equals() but have different logical types, then both of the following cases are possible:
> * The two instances may accidentally have the same hash, which is consistent with the equals() method but is pure coincidence and has a very low probablility.
> * The two instances may have different hashes and end up in different buckets of a hash map, leading to a situation where we can't find a value in the hash map despite that it's equals() would return true.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)