[ 
https://issues.apache.org/jira/browse/FLINK-10438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-10438:
-----------------------------------
    Labels: auto-deprioritized-major stale-minor  (was: 
auto-deprioritized-major)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issues has been marked as 
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is 
still Minor, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> Built in functions should document the returned types
> -----------------------------------------------------
>
>                 Key: FLINK-10438
>                 URL: https://issues.apache.org/jira/browse/FLINK-10438
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation, Table SQL / API
>    Affects Versions: 1.6.1
>            Reporter: Piotr Nowojski
>            Priority: Minor
>              Labels: auto-deprioritized-major, stale-minor
>
> As it is now, user have no idea to know whether the result of the operation 
> is accurate or not.
> For example {{POWER(4, 2)}} or {{POWER(2.5, )}} could return exact results 
> (with proper {{DECIMAL}}  support), while it seems like now they are silently 
> returning approximated result (because of {{DOUBLE}} arithmetic). Same 
> applies to other arithmetic functions, like {{COS SIN ATAN LOG ...}}.
> Such behaviour should be documented. In some cases documenting the argument 
> types also might be important.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to