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:44:03 UTC
[jira] [Created] (PARQUET-1191) Type.hashCode() takes originalType
into account but Type.equals() does not
Zoltan Ivanfi created PARQUET-1191:
--------------------------------------
Summary: 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: Zoltan Ivanfi
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)