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

Timo Walther commented on FLINK-13266:
--------------------------------------

[FLINK-13266][table] Port function-related descriptors to flink-table-common
Fixed in 1.9.0: 22538cc3827c3d483f4ca23fc52ae00b822706ba
Fixed in 1.10.0: 24f1dce1ceca35ef0177fa16648fd40cbcb52ded

> Relocate blink planner classes to avoid class clashes
> -----------------------------------------------------
>
>                 Key: FLINK-13266
>                 URL: https://issues.apache.org/jira/browse/FLINK-13266
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / Planner
>    Affects Versions: 1.9.0
>            Reporter: Jark Wu
>            Assignee: godfrey he
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 1.9.0, 1.10.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> We should have a list to relocate classes in {{flink-table-planner-blink}} 
> and {{flink-table-runtime-blink}} to avoid class clashes to make both 
> planners available in a lib directory.
> Note that, not all the classes can/should be relocated. For examples: calcite 
> classes, {{PlannerExpressionParserImpl}} and so on. 
> The relocation package name is up to discussion. A dedicated path is 
> {{org.apache.flink.table.blink}}.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to