You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jark Wu (Jira)" <ji...@apache.org> on 2019/10/12 13:00:00 UTC
[jira] [Updated] (FLINK-14367) Fully support for converting RexNode
to Expression
[ https://issues.apache.org/jira/browse/FLINK-14367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jark Wu updated FLINK-14367:
----------------------------
Description:
Currently, the {{RexNodeToExpressionConverter}} in both planners are not fully support. There're many RexNodes can not be converted to Expressions.
1) RexFieldAccess -> GET call
2) Literals in interval types and complex types and TimeUnitRange
3) TRIM(BOTH/LEADING/HEADING, ..)
...
We should have a comprehensive tests to cover all cases. A good idea is to verify with {{ExpressionConverter}} together.
was:
Currently, the {{RexNodeToExpressionConverter}} in both planners are not fully support. There're many RexNodes can not be converted to Expressions.
1) RexFieldAccess -> GET call
2) Literals in interval types and complex types
3) TRIM(BOTH/LEADING/HEADING, ..)
...
We should have a comprehensive tests to cover all cases. A good idea is to verify with {{ExpressionConverter}} together.
> Fully support for converting RexNode to Expression
> --------------------------------------------------
>
> Key: FLINK-14367
> URL: https://issues.apache.org/jira/browse/FLINK-14367
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
> Reporter: Jark Wu
> Priority: Major
>
> Currently, the {{RexNodeToExpressionConverter}} in both planners are not fully support. There're many RexNodes can not be converted to Expressions.
> 1) RexFieldAccess -> GET call
> 2) Literals in interval types and complex types and TimeUnitRange
> 3) TRIM(BOTH/LEADING/HEADING, ..)
> ...
> We should have a comprehensive tests to cover all cases. A good idea is to verify with {{ExpressionConverter}} together.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)