[
https://issues.apache.org/jira/browse/KYLIN-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173206#comment-15173206
]
Edward Zhang commented on KYLIN-1345:
-------------------------------------
I don't quite understand, are you saying it is frontend to set return data
type? If that is the case, I think moving the logic to frontend is the best
solution because it is related to modeling. When doing modeling, we know we
should use a different data type than that simply inherited from column data
type for the case of sum of decimal. When I say frontend, I don't mean
frontend, I mean service layer.
Let me know your thoughts on the fix.
> measure type expansion when dealing sum of decimal metric
> ---------------------------------------------------------
>
> Key: KYLIN-1345
> URL: https://issues.apache.org/jira/browse/KYLIN-1345
> Project: Kylin
> Issue Type: Improvement
> Reporter: hongbin ma
> Assignee: Edward Zhang
> Labels: newbie
>
> suppose a metric column price is of type decimal (6,2), the sum aggregator of
> it might exceed the maximal of decimal (6,2). Currently for metric
> aggregators we inherite the column's type in hive. We should think auto
> expanding decimal type to decimal(18,4) (just an example) for such cases
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
