Hanyu Zheng created FLINK-41573:
-----------------------------------
Summary: Reject a group window auxiliary function without a
matching GROUP BY window during validation
Key: FLINK-41573
URL: https://issues.apache.org/jira/browse/FLINK-41573
Project: Flink
Issue Type: Improvement
Components: Table SQL / Planner
Affects Versions: 2.3.0
Reporter: Hanyu Zheng
Fix For: 2.3.0
A group window auxiliary function such as TUMBLE_START, TUMBLE_END, HOP_START
or SESSION_START is only rewritten when a GROUP BY uses the same window.
Without one, the call reaches the ExprCodeGenerator fallback. This happens in
both batch and streaming mode.
{code:sql}
-- no GROUP BY
SELECT TUMBLE_START(ts, INTERVAL '10' SECOND) FROM T;
-- the GROUP BY window uses a different interval
SELECT TUMBLE_START(ts, INTERVAL '10' SECOND), COUNT(*) FROM T GROUP BY
TUMBLE(ts, INTERVAL '1' MINUTE);
{code}
{noformat}
Unsupported call: TUMBLE_START(TIMESTAMP_LTZ(3), INTERVAL SECOND(3) NOT NULL)
If you think this function should be supported, you can create an issue and
start a discussion for it.
{noformat}
This is a query error, but the message reads like a missing feature. The
validator should reject the call and say that it needs a GROUP BY window with
the same time attribute and interval. FLINK-23422 is related: it covers an
auxiliary function used inside an aggregate.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)