[
https://issues.apache.org/jira/browse/FLINK-6124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934032#comment-15934032
]
ASF GitHub Bot commented on FLINK-6124:
---------------------------------------
GitHub user docete opened a pull request:
https://github.com/apache/flink/pull/3579
[FLINK-6124] [Table API & SQL] support max/min aggregations for strin…
currently min/max aggregations on string type is not supported and should
be added.
When min/max aggregations are used on string column, return min/max value
by lexicographically order.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/docete/flink master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3579.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3579
----
commit d4c8efd34c2b1b26318452082d8c2ab3925a0411
Author: Zhenghua Gao <[email protected]>
Date: 2017-03-20T11:29:31Z
[FLINK-6124] [Table API & SQL] support max/min aggregations for string type
----
> support max/min aggregations for string type
> --------------------------------------------
>
> Key: FLINK-6124
> URL: https://issues.apache.org/jira/browse/FLINK-6124
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Reporter: Zhenghua Gao
> Assignee: Zhenghua Gao
>
> Recently when I port some query to Flink SQL, I found currently min/max
> aggregations on string type is not supported and should be added.
> When min/max aggregations are used on string column, return min/max value by
> lexicographically order.
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
