You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "BELUGA BEHR (JIRA)" <ji...@apache.org> on 2019/02/13 13:25:00 UTC
[jira] [Assigned] (HIVE-21264) Improvements Around CharTypeInfo
[ https://issues.apache.org/jira/browse/HIVE-21264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
BELUGA BEHR reassigned HIVE-21264:
----------------------------------
Assignee: BELUGA BEHR
> Improvements Around CharTypeInfo
> --------------------------------
>
> Key: HIVE-21264
> URL: https://issues.apache.org/jira/browse/HIVE-21264
> Project: Hive
> Issue Type: Improvement
> Affects Versions: 4.0.0, 3.2.0
> Reporter: BELUGA BEHR
> Assignee: BELUGA BEHR
> Priority: Minor
>
> The {{CharTypeInfo}} stores the type name of the data type (char/varchar) and the length (1-255). {{CharTypeInfo}} objects are often getting cached once they are created.
> The {hashcode()} and {{equals()}} of its sub-classes varchar and char are inconsistent in this regard.
> * Make hashcode and equals consistent (and fast)
> * Simplify the {{getQualifiedName}} implementation and reduce the scope to protected
> * Other related nits
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)