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/07/24 08:45:00 UTC

[jira] [Resolved] (FLINK-13266) Relocate blink planner classes to avoid class clashes

     [ https://issues.apache.org/jira/browse/FLINK-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jark Wu resolved FLINK-13266.
-----------------------------
    Resolution: Fixed

> 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: 0.5h
>  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)