[
https://issues.apache.org/jira/browse/TAJO-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13842074#comment-13842074
]
Jihoon Son commented on TAJO-391:
---------------------------------
Right.
My above comment means that supporting more precise types is required to get
the exact results.
Thus this is just a temporal solution to get more precise results.
However, I can't understand why the problem is occurred for only when the
function parameters are the constant values.
The internal representations are same for whether the values are from user
inputs or stored data.
> Change setting default type in query from FLOAT4 to FLOAT8
> ----------------------------------------------------------
>
> Key: TAJO-391
> URL: https://issues.apache.org/jira/browse/TAJO-391
> Project: Tajo
> Issue Type: Improvement
> Components: operator/function/udf
> Reporter: DaeMyung Kang
> Assignee: DaeMyung Kang
> Priority: Minor
> Fix For: 0.8-incubating
>
> Attachments: TAJO-391.patch
>
>
> FLOAT4 is default parsed float type in tajo.
> but it can cause some trobles when we use it as FLOAT8.
> for examples.
> 0.4(f) will changed to 0.40000000000005(d)
> so it cause different result from java.Math functions.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
