[
https://issues.apache.org/jira/browse/FLINK-11191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Walther closed FLINK-11191.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.8.0
1.7.2
Fixed in 1.8: 392647d09cc43ea94a53aa56d8c46bfe7d16d53e
Fixed in 1.7: b195472c0e513bc8afc36c5761edf2680e7a6f5b
> Exception in code generation when ambiguous columns in MATCH_RECOGNIZE
> ----------------------------------------------------------------------
>
> Key: FLINK-11191
> URL: https://issues.apache.org/jira/browse/FLINK-11191
> Project: Flink
> Issue Type: Bug
> Components: Table API & SQL
> Affects Versions: 1.7.0, 1.8.0
> Reporter: Dawid Wysakowicz
> Assignee: Dawid Wysakowicz
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.2, 1.8.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Query:
> {code}
> SELECT *
> FROM Ticker
> MATCH_RECOGNIZE (
> PARTITION BY symbol, price
> ORDER BY proctime
> MEASURES
> A.symbol AS symbol,
> A.price AS price
> PATTERN (A)
> DEFINE
> A AS symbol = 'a'
> ) AS T
> {code}
> throws a cryptic exception from the code generation stack that the output
> arity is wrong. We should add early validation and throw a meaningful
> exception.
> I've also created a calcite ticket to fix it on calcite's side: [CALCITE-2747]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
