flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-10340) Add Cosh math function supported in Table API and SQL
Date Mon, 01 Oct 2018 09:05:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-10340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16633740#comment-16633740
] 

ASF GitHub Bot commented on FLINK-10340:
----------------------------------------

pnowojski commented on a change in pull request #6700: [FLINK-10340][table] Add Cosh math
function supported in Table API and SQL
URL: https://github.com/apache/flink/pull/6700#discussion_r221537661
 
 

 ##########
 File path: docs/dev/table/functions.md
 ##########
 @@ -1274,6 +1274,17 @@ ATAN2(numeric1, numeric2)
       </td>
     </tr>
 
+    <tr>
+      <td>
+        {% highlight text %}
+COSH(numeric)
+{% endhighlight %}
+      </td>
+      <td>
+        <p>Returns the hyperbolic cosine of <i>numeric</i>. Return value
type is DOUBLE.</p>
 
 Review comment:
   @xccui if you think using `<i>` is better I'm fine with that, I don't mind one way
or the other.
   
   However I don't understand:
   
   > before reaching a consensus about the format and the internal implementation, I suggest
to keep the current doc style, i.e., without mentioning the return type, for now.
   
   We are already following a convention that for all of the math functions we are dropping
precision and returning `double`. What's the point of not documenting it?
   
   If you could guarantee me that we will document those return types lets say within a month,
I would be fine with postponing it. However I don't believe something like that would happen,
so I prefer to incrementally start adding this return type information right now. Later if
someone will want, we can reformat the page. I do not see any downside to such incremental
approach until that moment.
   
   > why still indicating the return type for each numeric function explicitly? How about
adding a single note for that?
   
   since some of them can be implemented precisely (`abs`, `min`, `max`, `ceil`, ...), others
can be for some variants (`power(DECIMAL, INT)`). We can state this general rule that functions
returning `DOUBLE` are approximations, but we still need specific information for every function,
whether it returns approximated (`DOUBLE`) or precise (`DECIMAL`) result. 
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Add Cosh math function supported in Table API and SQL
> -----------------------------------------------------
>
>                 Key: FLINK-10340
>                 URL: https://issues.apache.org/jira/browse/FLINK-10340
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table API &amp; SQL
>    Affects Versions: 1.6.0
>            Reporter: Sergey Tsvetkov
>            Assignee: vinoyang
>            Priority: Minor
>              Labels: pull-request-available
>
> Implement udf of cosh, just like in oracle
> [https://docs.oracle.com/cd/B28359_01/server.111/b28286/functions031.htm#SQLRF00623]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message