[
https://issues.apache.org/jira/browse/FLINK-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15473128#comment-15473128
]
Timo Walther commented on FLINK-4597:
-------------------------------------
I thought the same. I'm currently reworking the SQL documentation as part of
FLINK-4549. So that all functions (including the implicit ones) are documented.
I will use the syntax Calcite is using {{boolean1 OR boolean2}}, {{value1 <>
value2}}. What do you think?
> Improve Scalar Function section in Table API documentation
> ----------------------------------------------------------
>
> Key: FLINK-4597
> URL: https://issues.apache.org/jira/browse/FLINK-4597
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Reporter: Jark Wu
> Assignee: Jark Wu
> Priority: Minor
>
> The function signature in Scalar Function section is a little confusing.
> Because it's hard to distinguish keyword and parameters. Such as :
> {{EXTRACT(TIMEINTERVALUNIT FROM TEMPORAL)}}, user may not know TEMPORAL is a
> parameter after first glance. I propose to use {{<>}} around parameters, i.e.
> {{EXTRACT(<TIMEINTERVALUNIT> FROM <TEMPORAL>)}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
