[
https://issues.apache.org/jira/browse/FLINK-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891611#comment-16891611
]
Jark Wu edited comment on FLINK-13266 at 7/24/19 8:43 AM:
----------------------------------------------------------
[FLINK-13266][table] Move OptimizerConfigOptions & ExecutionConfigOptions to
table-api-java module
Fixed in 1.10.0: 66e55d60f819c5a1f809830190461fb6ac341b0b
Fixed in 1.9.0: df1d788e89c0ee961e64a663e47d3f4cee3ccd70
was (Author: jark):
[FLINK-13266][table] Move OptimizerConfigOptions & ExecutionConfigOptions to
table-api-java module
Fixed in 1.10.0: 66e55d60f819c5a1f809830190461fb6ac341b0b
Fixed in 1.9.0: TODO
> 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)
