You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Renjie Liu (JIRA)" <ji...@apache.org> on 2018/03/16 02:25:00 UTC

[jira] [Commented] (FLINK-8953) Resolve unresolved field references in FieldComputer expressions

    [ https://issues.apache.org/jira/browse/FLINK-8953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16401391#comment-16401391 ] 

Renjie Liu commented on FLINK-8953:
-----------------------------------

Hi, Tim:

I want to look into this, could you assign this to me?

> Resolve unresolved field references in FieldComputer expressions
> ----------------------------------------------------------------
>
>                 Key: FLINK-8953
>                 URL: https://issues.apache.org/jira/browse/FLINK-8953
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API &amp; SQL
>            Reporter: Timo Walther
>            Priority: Major
>
> When implementing the {{FieldComputer.getExpression}} method, it is not possible to use API classes but only internal expression case classes.
> It would be great to also define timestamp extractors like:
> {code}
>   def getExpression(fieldAccesses: Array[ResolvedFieldReference]): Expression = {
>     // 'x.cast(Types.LONG)
>     // ExpressionParser.parseExpression("x.cast(LONG)")
>   }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)