[jira] [Commented] (FLINK-7464) Add useful build-in Aggregate function into TabalAPI
[ https://issues.apache.org/jira/browse/FLINK-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16812283#comment-16812283 ] Lifei Chen commented on FLINK-7464: --- Hi, [~sunjincheng121], I think `FIRST_VALUE` and `LAST_VALUE` are very useful and I can also find the two build-in aggregate functions docs of [aliyun|[https://help.aliyun.com/knowledge_detail/62791.html]]. But the subtask is closed with status unsolved. is there any reasons why the progress of the feature is stopped ? Thanks ! > Add useful build-in Aggregate function into TabalAPI > > > Key: FLINK-7464 > URL: https://issues.apache.org/jira/browse/FLINK-7464 > Project: Flink > Issue Type: New Feature > Components: Table SQL / API >Reporter: sunjincheng >Priority: Major > > In this JIRA, will create some sub-task for add specific build-in aggregate > function, such as FIRST_VALUE, LAST_VALUE, BloomFilterCount etc. > Welcome anybody to add the sub-task. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FLINK-11819) Additional attribute for order by not support by flink sql, but told supported in doc
[
https://issues.apache.org/jira/browse/FLINK-11819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16793760#comment-16793760
]
Lifei Chen commented on FLINK-11819:
Ok, I will close the issue.
Best, Lifei
> Additional attribute for order by not support by flink sql, but told
> supported in doc
> -
>
> Key: FLINK-11819
> URL: https://issues.apache.org/jira/browse/FLINK-11819
> Project: Flink
> Issue Type: Bug
> Components: Documentation
>Affects Versions: 1.7.2
>Reporter: Lifei Chen
>Assignee: Lifei Chen
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.3
>
> Original Estimate: 3h
> Time Spent: 20m
> Remaining Estimate: 2h 40m
>
> I am using flink v1.7.1, when I use flink sql to order by an attribute (not
> time attribute), the error logs is as follow.
>
> sql:
> {quote}"SELECT * FROM events order by tenantId"
> {quote}
>
> error logs:
> {quote}Exception in thread "main" org.apache.flink.table.api.TableException:
> Cannot generate a valid execution plan for the given query:
> FlinkLogicalSort(sort0=[$2], dir0=[ASC])
> FlinkLogicalNativeTableScan(table=[[_DataStreamTable_0]])
> This exception indicates that the query uses an unsupported SQL feature.
> Please check the documentation for the set of currently supported SQL
> features.
> at
> org.apache.flink.table.api.TableEnvironment.runVolcanoPlanner(TableEnvironment.scala:377)
> at
> org.apache.flink.table.api.TableEnvironment.optimizePhysicalPlan(TableEnvironment.scala:302)
> at
> org.apache.flink.table.api.StreamTableEnvironment.optimize(StreamTableEnvironment.scala:814)
> at
> org.apache.flink.table.api.StreamTableEnvironment.translate(StreamTableEnvironment.scala:860)
> at
> org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:305)
> at
> org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:248)
> {quote}
>
> So as for now, only time attribute is supported by flink for command `order
> by`, additional attribute is not supported yet, Is that right ?
> If so, there is a mistake, indicated that other attribute except for `time
> attribute` is supported .
> related links:
> [https://ci.apache.org/projects/flink/flink-docs-release-1.7/dev/table/sql.html#orderby--limit]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (FLINK-11819) Additional attribute for order by not support by flink sql, but told supported in doc
[
https://issues.apache.org/jira/browse/FLINK-11819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lifei Chen closed FLINK-11819.
--
Resolution: Won't Do
> Additional attribute for order by not support by flink sql, but told
> supported in doc
> -
>
> Key: FLINK-11819
> URL: https://issues.apache.org/jira/browse/FLINK-11819
> Project: Flink
> Issue Type: Bug
> Components: Documentation
>Affects Versions: 1.7.2
>Reporter: Lifei Chen
>Assignee: Lifei Chen
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.3
>
> Original Estimate: 3h
> Time Spent: 20m
> Remaining Estimate: 2h 40m
>
> I am using flink v1.7.1, when I use flink sql to order by an attribute (not
> time attribute), the error logs is as follow.
>
> sql:
> {quote}"SELECT * FROM events order by tenantId"
> {quote}
>
> error logs:
> {quote}Exception in thread "main" org.apache.flink.table.api.TableException:
> Cannot generate a valid execution plan for the given query:
> FlinkLogicalSort(sort0=[$2], dir0=[ASC])
> FlinkLogicalNativeTableScan(table=[[_DataStreamTable_0]])
> This exception indicates that the query uses an unsupported SQL feature.
> Please check the documentation for the set of currently supported SQL
> features.
> at
> org.apache.flink.table.api.TableEnvironment.runVolcanoPlanner(TableEnvironment.scala:377)
> at
> org.apache.flink.table.api.TableEnvironment.optimizePhysicalPlan(TableEnvironment.scala:302)
> at
> org.apache.flink.table.api.StreamTableEnvironment.optimize(StreamTableEnvironment.scala:814)
> at
> org.apache.flink.table.api.StreamTableEnvironment.translate(StreamTableEnvironment.scala:860)
> at
> org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:305)
> at
> org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:248)
> {quote}
>
> So as for now, only time attribute is supported by flink for command `order
> by`, additional attribute is not supported yet, Is that right ?
> If so, there is a mistake, indicated that other attribute except for `time
> attribute` is supported .
> related links:
> [https://ci.apache.org/projects/flink/flink-docs-release-1.7/dev/table/sql.html#orderby--limit]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (FLINK-11819) Additional attribute for order by not support by flink sql, but told supported in doc
[
https://issues.apache.org/jira/browse/FLINK-11819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16789196#comment-16789196
]
Lifei Chen commented on FLINK-11819:
[~xccui] you are right, I have a misunderstanding about the doc.
[~hequn8128]，It is better to give a more detailed description about the example
to avoid others having the same trouble as me. I will try to give a pr for
updating the doc.
> Additional attribute for order by not support by flink sql, but told
> supported in doc
> -
>
> Key: FLINK-11819
> URL: https://issues.apache.org/jira/browse/FLINK-11819
> Project: Flink
> Issue Type: Bug
> Components: Documentation
>Affects Versions: 1.7.2
>Reporter: Lifei Chen
>Assignee: Lifei Chen
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.3
>
> Original Estimate: 3h
> Time Spent: 20m
> Remaining Estimate: 2h 40m
>
> I am using flink v1.7.1, when I use flink sql to order by an attribute (not
> time attribute), the error logs is as follow.
>
> sql:
> {quote}"SELECT * FROM events order by tenantId"
> {quote}
>
> error logs:
> {quote}Exception in thread "main" org.apache.flink.table.api.TableException:
> Cannot generate a valid execution plan for the given query:
> FlinkLogicalSort(sort0=[$2], dir0=[ASC])
> FlinkLogicalNativeTableScan(table=[[_DataStreamTable_0]])
> This exception indicates that the query uses an unsupported SQL feature.
> Please check the documentation for the set of currently supported SQL
> features.
> at
> org.apache.flink.table.api.TableEnvironment.runVolcanoPlanner(TableEnvironment.scala:377)
> at
> org.apache.flink.table.api.TableEnvironment.optimizePhysicalPlan(TableEnvironment.scala:302)
> at
> org.apache.flink.table.api.StreamTableEnvironment.optimize(StreamTableEnvironment.scala:814)
> at
> org.apache.flink.table.api.StreamTableEnvironment.translate(StreamTableEnvironment.scala:860)
> at
> org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:305)
> at
> org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:248)
> {quote}
>
> So as for now, only time attribute is supported by flink for command `order
> by`, additional attribute is not supported yet, Is that right ?
> If so, there is a mistake, indicated that other attribute except for `time
> attribute` is supported .
> related links:
> [https://ci.apache.org/projects/flink/flink-docs-release-1.7/dev/table/sql.html#orderby--limit]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (FLINK-11819) Additional attribute for order by not support by flink sql, but told supported in doc
[
https://issues.apache.org/jira/browse/FLINK-11819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785168#comment-16785168
]
Lifei Chen commented on FLINK-11819:
Thanks [~xccui], maybe I have a misunderstanding about the doc, I will try it
again today, and give you feedback!
> Additional attribute for order by not support by flink sql, but told
> supported in doc
> -
>
> Key: FLINK-11819
> URL: https://issues.apache.org/jira/browse/FLINK-11819
> Project: Flink
> Issue Type: Bug
> Components: Documentation
>Affects Versions: 1.7.2
>Reporter: Lifei Chen
>Assignee: Lifei Chen
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.3
>
> Original Estimate: 3h
> Time Spent: 10m
> Remaining Estimate: 2h 50m
>
> I am using flink v1.7.1, when I use flink sql to order by an attribute (not
> time attribute), the error logs is as follow.
>
> sql:
> {quote}"SELECT * FROM events order by tenantId"
> {quote}
>
> error logs:
> {quote}Exception in thread "main" org.apache.flink.table.api.TableException:
> Cannot generate a valid execution plan for the given query:
> FlinkLogicalSort(sort0=[$2], dir0=[ASC])
> FlinkLogicalNativeTableScan(table=[[_DataStreamTable_0]])
> This exception indicates that the query uses an unsupported SQL feature.
> Please check the documentation for the set of currently supported SQL
> features.
> at
> org.apache.flink.table.api.TableEnvironment.runVolcanoPlanner(TableEnvironment.scala:377)
> at
> org.apache.flink.table.api.TableEnvironment.optimizePhysicalPlan(TableEnvironment.scala:302)
> at
> org.apache.flink.table.api.StreamTableEnvironment.optimize(StreamTableEnvironment.scala:814)
> at
> org.apache.flink.table.api.StreamTableEnvironment.translate(StreamTableEnvironment.scala:860)
> at
> org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:305)
> at
> org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:248)
> {quote}
>
> So as for now, only time attribute is supported by flink for command `order
> by`, additional attribute is not supported yet, Is that right ?
> If so, there is a mistake, indicated that other attribute except for `time
> attribute` is supported .
> related links:
> [https://ci.apache.org/projects/flink/flink-docs-release-1.7/dev/table/sql.html#orderby--limit]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FLINK-11819) Additional attribute for order by not support by flink sql, but told supported in doc
[
https://issues.apache.org/jira/browse/FLINK-11819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lifei Chen updated FLINK-11819:
---
Description:
I am using flink v1.7.1, when I use flink sql to order by an attribute (not
time attribute), the error logs is as follow.
sql:
{quote}"SELECT * FROM events order by tenantId"
{quote}
error logs:
{quote}Exception in thread "main" org.apache.flink.table.api.TableException:
Cannot generate a valid execution plan for the given query:
FlinkLogicalSort(sort0=[$2], dir0=[ASC])
FlinkLogicalNativeTableScan(table=[[_DataStreamTable_0]])
This exception indicates that the query uses an unsupported SQL feature.
Please check the documentation for the set of currently supported SQL features.
at
org.apache.flink.table.api.TableEnvironment.runVolcanoPlanner(TableEnvironment.scala:377)
at
org.apache.flink.table.api.TableEnvironment.optimizePhysicalPlan(TableEnvironment.scala:302)
at
org.apache.flink.table.api.StreamTableEnvironment.optimize(StreamTableEnvironment.scala:814)
at
org.apache.flink.table.api.StreamTableEnvironment.translate(StreamTableEnvironment.scala:860)
at
org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:305)
at
org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:248)
{quote}
So as for now, only time attribute is supported by flink for command `order
by`, additional attribute is not supported yet, Is that right ?
If so, there is a mistake, indicated that other attribute except for `time
attribute` is supported .
related links:
[https://ci.apache.org/projects/flink/flink-docs-release-1.7/dev/table/sql.html#orderby--limit]
was:
I am using flink v1.7.1, when I use flink sql to order by an attribute (not
time attribute), the error logs is as follow.
sql:
```
"SELECT * FROM events order by tenantId"
```
```
Exception in thread "main" org.apache.flink.table.api.TableException: Cannot
generate a valid execution plan for the given query:
FlinkLogicalSort(sort0=[$2], dir0=[ASC])
FlinkLogicalNativeTableScan(table=[[_DataStreamTable_0]])
This exception indicates that the query uses an unsupported SQL feature.
Please check the documentation for the set of currently supported SQL features.
at
org.apache.flink.table.api.TableEnvironment.runVolcanoPlanner(TableEnvironment.scala:377)
at
org.apache.flink.table.api.TableEnvironment.optimizePhysicalPlan(TableEnvironment.scala:302)
at
org.apache.flink.table.api.StreamTableEnvironment.optimize(StreamTableEnvironment.scala:814)
at
org.apache.flink.table.api.StreamTableEnvironment.translate(StreamTableEnvironment.scala:860)
at
org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:305)
at
org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:248)
```
So as for no, only time attribute is supported by flink for command `order by`,
additional attribute is not supported yet, Is that right ?
If so, there is a mistake, indicated that other attribute except for `time
attribute` is supported .
related links:
[https://ci.apache.org/projects/flink/flink-docs-release-1.7/dev/table/sql.html#orderby--limit]
> Additional attribute for order by not support by flink sql, but told
> supported in doc
> -
>
> Key: FLINK-11819
> URL: https://issues.apache.org/jira/browse/FLINK-11819
> Project: Flink
> Issue Type: Bug
> Components: Documentation
>Affects Versions: 1.7.2
>Reporter: Lifei Chen
>Assignee: Lifei Chen
>Priority: Major
> Fix For: 1.7.3
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> I am using flink v1.7.1, when I use flink sql to order by an attribute (not
> time attribute), the error logs is as follow.
>
> sql:
> {quote}"SELECT * FROM events order by tenantId"
> {quote}
>
> error logs:
> {quote}Exception in thread "main" org.apache.flink.table.api.TableException:
> Cannot generate a valid execution plan for the given query:
> FlinkLogicalSort(sort0=[$2], dir0=[ASC])
> FlinkLogicalNativeTableScan(table=[[_DataStreamTable_0]])
> This exception indicates that the query uses an unsupported SQL feature.
> Please check the documentation for the set of currently supported SQL
> features.
> at
> org.apache.flink.table.api.TableEnvironment.runVolcanoPlanner(TableEnvironment.scala:377)
> at
> org.apache.flink.table.api.TableEnvironment.optimizePhysicalPlan(TableEnvironment.scala:302)
> at
> org.apache.flink.table.api.StreamTableEnvironment.optimize(StreamTableEnvironment.scala:814)
> at
> org.apache.flink.table.api.StreamTableEnvironment.translate(StreamTableEnvironment.scala:860)
> at
>
[jira] [Updated] (FLINK-11819) Additional attribute for order by not support by flink sql, but told supported in doc
[ https://issues.apache.org/jira/browse/FLINK-11819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lifei Chen updated FLINK-11819: --- Description: I am using flink v1.7.1, when I use flink sql to order by an attribute (not time attribute), the error logs is as follow. sql: ``` "SELECT * FROM events order by tenantId" ``` ``` Exception in thread "main" org.apache.flink.table.api.TableException: Cannot generate a valid execution plan for the given query: FlinkLogicalSort(sort0=[$2], dir0=[ASC]) FlinkLogicalNativeTableScan(table=[[_DataStreamTable_0]]) This exception indicates that the query uses an unsupported SQL feature. Please check the documentation for the set of currently supported SQL features. at org.apache.flink.table.api.TableEnvironment.runVolcanoPlanner(TableEnvironment.scala:377) at org.apache.flink.table.api.TableEnvironment.optimizePhysicalPlan(TableEnvironment.scala:302) at org.apache.flink.table.api.StreamTableEnvironment.optimize(StreamTableEnvironment.scala:814) at org.apache.flink.table.api.StreamTableEnvironment.translate(StreamTableEnvironment.scala:860) at org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:305) at org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:248) ``` So as for no, only time attribute is supported by flink for command `order by`, additional attribute is not supported yet, Is that right ? If so, there is a mistake, indicated that other attribute except for `time attribute` is supported . related links: [https://ci.apache.org/projects/flink/flink-docs-release-1.7/dev/table/sql.html#orderby--limit] was: I am using flink v1.7.1, when I use flink sql to order by an attribute (not time attribute), the error logs is as follow. ``` Exception in thread "main" org.apache.flink.table.api.TableException: Cannot generate a valid execution plan for the given query: FlinkLogicalSort(sort0=[$2], dir0=[ASC]) FlinkLogicalNativeTableScan(table=[[_DataStreamTable_0]]) This exception indicates that the query uses an unsupported SQL feature. Please check the documentation for the set of currently supported SQL features. at org.apache.flink.table.api.TableEnvironment.runVolcanoPlanner(TableEnvironment.scala:377) at org.apache.flink.table.api.TableEnvironment.optimizePhysicalPlan(TableEnvironment.scala:302) at org.apache.flink.table.api.StreamTableEnvironment.optimize(StreamTableEnvironment.scala:814) at org.apache.flink.table.api.StreamTableEnvironment.translate(StreamTableEnvironment.scala:860) at org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:305) at org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:248) ``` So as for no, only time attribute is supported by flink for command `order by`, additional attribute is not supported yet, Is that right ? If so, there is a mistake, indicated that other attribute except for `time attribute` is supported . related links: https://ci.apache.org/projects/flink/flink-docs-release-1.7/dev/table/sql.html#orderby--limit > Additional attribute for order by not support by flink sql, but told > supported in doc > - > > Key: FLINK-11819 > URL: https://issues.apache.org/jira/browse/FLINK-11819 > Project: Flink > Issue Type: Bug > Components: Documentation >Affects Versions: 1.7.2 >Reporter: Lifei Chen >Assignee: Lifei Chen >Priority: Major > Fix For: 1.7.3 > > Original Estimate: 3h > Remaining Estimate: 3h > > I am using flink v1.7.1, when I use flink sql to order by an attribute (not > time attribute), the error logs is as follow. > > sql: > ``` > "SELECT * FROM events order by tenantId" > ``` > ``` > Exception in thread "main" org.apache.flink.table.api.TableException: Cannot > generate a valid execution plan for the given query: > FlinkLogicalSort(sort0=[$2], dir0=[ASC]) > FlinkLogicalNativeTableScan(table=[[_DataStreamTable_0]]) > This exception indicates that the query uses an unsupported SQL feature. > Please check the documentation for the set of currently supported SQL > features. > at > org.apache.flink.table.api.TableEnvironment.runVolcanoPlanner(TableEnvironment.scala:377) > at > org.apache.flink.table.api.TableEnvironment.optimizePhysicalPlan(TableEnvironment.scala:302) > at > org.apache.flink.table.api.StreamTableEnvironment.optimize(StreamTableEnvironment.scala:814) > at > org.apache.flink.table.api.StreamTableEnvironment.translate(StreamTableEnvironment.scala:860) > at > org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:305) > at >
[jira] [Created] (FLINK-11819) Additional attribute for order by not support by flink sql, but told supported in doc
Lifei Chen created FLINK-11819: -- Summary: Additional attribute for order by not support by flink sql, but told supported in doc Key: FLINK-11819 URL: https://issues.apache.org/jira/browse/FLINK-11819 Project: Flink Issue Type: Bug Components: Documentation Affects Versions: 1.7.2 Reporter: Lifei Chen Assignee: Lifei Chen Fix For: 1.7.3 I am using flink v1.7.1, when I use flink sql to order by an attribute (not time attribute), the error logs is as follow. ``` Exception in thread "main" org.apache.flink.table.api.TableException: Cannot generate a valid execution plan for the given query: FlinkLogicalSort(sort0=[$2], dir0=[ASC]) FlinkLogicalNativeTableScan(table=[[_DataStreamTable_0]]) This exception indicates that the query uses an unsupported SQL feature. Please check the documentation for the set of currently supported SQL features. at org.apache.flink.table.api.TableEnvironment.runVolcanoPlanner(TableEnvironment.scala:377) at org.apache.flink.table.api.TableEnvironment.optimizePhysicalPlan(TableEnvironment.scala:302) at org.apache.flink.table.api.StreamTableEnvironment.optimize(StreamTableEnvironment.scala:814) at org.apache.flink.table.api.StreamTableEnvironment.translate(StreamTableEnvironment.scala:860) at org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:305) at org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:248) ``` So as for no, only time attribute is supported by flink for command `order by`, additional attribute is not supported yet, Is that right ? If so, there is a mistake, indicated that other attribute except for `time attribute` is supported . related links: https://ci.apache.org/projects/flink/flink-docs-release-1.7/dev/table/sql.html#orderby--limit -- This message was sent by Atlassian JIRA (v7.6.3#76005)
