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

Timo Walther commented on FLINK-11908:
--------------------------------------

I think [~dawidwys] is facing similar issues with the expression parser. We 
discussed it offline and agreed on not porting the expression parser for now 
and look for better alternatives (FLINK-11890). Until then we could simply 
perform a reflection-based classpath search for the parser class. 
{{ExpressionParser.parseExpression()}} will search for {{ExpressionParserImpl}} 
and call it. This unblocks all implementations in {{flink-table-api-java}}. 
What do you think?

> Port window classes into flink-api-java
> ---------------------------------------
>
>                 Key: FLINK-11908
>                 URL: https://issues.apache.org/jira/browse/FLINK-11908
>             Project: Flink
>          Issue Type: Sub-task
>          Components: API / Table SQL
>            Reporter: Hequn Cheng
>            Assignee: Hequn Cheng
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> As discussed in FLINK-11068, it is good to open a separate issue for porting 
> the window classes before opening a PR for the {{Table}} classes. This can 
> make our PR smaller thus will be better to be reviewed.



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

Reply via email to