[
https://issues.apache.org/jira/browse/FLINK-15678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-15678:
-----------------------------------
Labels: stale-major (was: )
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
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Optimize producing primary key without row number in special Top 1
> ------------------------------------------------------------------
>
> Key: FLINK-15678
> URL: https://issues.apache.org/jira/browse/FLINK-15678
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
> Reporter: Jingsong Lee
> Priority: Major
> Labels: stale-major
>
> {code:java}
> SELECT c1, c2, c3, c4
> FROM (
> SELECT *,ROW_NUMBER() OVER (PARTITION BY c1, c2, c3 ORDER BY c4 DESC) AS
> rownum
> FROM t
> ) WHERE rownum <= 1
> {code}
> This SQL is Top 1, Top N produce stream with primary keys contains row
> number, but your sql didn't select row number, so there is not primary key.
> But for Top 1, we can produce primary key, because row number is always 1.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
