[
https://issues.apache.org/jira/browse/HIVE-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604478#comment-14604478
]
Xuefu Zhang commented on HIVE-10616:
------------------------------------
Agreed with Alex, I don't think there is any issue. Metadata always comes with
two parameters, even if user omits some in which case default is filled in. As
noted in the comments, the only chance that you might no parameters at all is
in the metadata migrated from that prior to decimal precision/scale support
where no parameters are stored. I believe that it's impossible to have a case
where there is only one parameter (precision) stored in the metadata.
Please provide a repro case otherwise.
> TypeInfoUtils doesn't handle DECIMAL with just precision specified
> ------------------------------------------------------------------
>
> Key: HIVE-10616
> URL: https://issues.apache.org/jira/browse/HIVE-10616
> Project: Hive
> Issue Type: Bug
> Components: Serializers/Deserializers
> Affects Versions: 1.0.0
> Reporter: Thomas Friedrich
> Assignee: Thomas Friedrich
> Priority: Minor
> Attachments: HIVE-10616.1.patch
>
>
> The parseType method in TypeInfoUtils doesn't handle decimal types with just
> precision specified although that's a valid type definition.
> As a result, TypeInfoUtils.getTypeInfoFromTypeString will always return
> decimal(10,0) for any decimal(<precision>) string.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
