[
https://issues.apache.org/jira/browse/FLINK-3728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabian Hueske updated FLINK-3728:
---------------------------------
Description:
We must explicitly exclude unsupported SQL features such as Grouping Sets from
being translated to Flink programs.
Otherwise, the resulting program will compute invalid results.
For that we must restrict the Calcite rules that translate Logical {{RelNodes}}
into {{DataSetRel}} or {{DataStreamRel}} nodes.
We may only translate to {{DataSetRel}} or {{DataStreamRel}} nodes if these
support the semantics of the {{RelNode}}.
Not translating a {{RelNode}} will yield a Calcite {{CannotPlanException}} that
we should catch and enrich with a meaningful error message.
was:
We should find a way to exclude unsupported SQL features such as outer joins,
intersection, etc..
A query like the following
{code}
SELECT c, g FROM t1 FULL OUTER JOIN t2 ON b = e
{code}
will currently not fail, but be translated into an inner join instead.
> Throw meaningful exceptions for unsupported SQL features
> --------------------------------------------------------
>
> Key: FLINK-3728
> URL: https://issues.apache.org/jira/browse/FLINK-3728
> Project: Flink
> Issue Type: Bug
> Components: Table API
> Affects Versions: 1.1.0
> Reporter: Vasia Kalavri
>
> We must explicitly exclude unsupported SQL features such as Grouping Sets
> from being translated to Flink programs.
> Otherwise, the resulting program will compute invalid results.
> For that we must restrict the Calcite rules that translate Logical
> {{RelNodes}} into {{DataSetRel}} or {{DataStreamRel}} nodes.
> We may only translate to {{DataSetRel}} or {{DataStreamRel}} nodes if these
> support the semantics of the {{RelNode}}.
> Not translating a {{RelNode}} will yield a Calcite {{CannotPlanException}}
> that we should catch and enrich with a meaningful error message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
