[FLINK-13267] Making it possible to have both flink planner and blink planner in classpath

• Type: Improvement
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.9.0
• Fix Version/s: 1.9.0
• Component/s: Table SQL / Planner
• Assignee: Jark Wu
• Reporter: Jark Wu
• Created: 15/Jul/19 11:30
• Updated: 27/Apr/21 18:05
• Resolved: 06/Aug/19 09:58

Description

In order to have a good experience for users when switching different planners, we want to have both flink planner and blink planner in one classpath. So that, users can not care about cluster setup when changing planner.

This is an umbrella issue to track all the problems need to fix before this can happen. A detailed problems is listed in the google doc: https://docs.google.com/document/d/15Z1Khy23DwDBp956yBzkMYkGdoQAU_QgBoJmFWSffow/edit#

Issue Links

• blocks: FLINK-13273 Allow switching planners in SQL Client

Sub-Tasks

• Remove planner class clashes for planner type inference lookups: Closed
• Relocate blink planner classes to avoid class clashes: Resolved
• Revert SqlSplittableAggFunction to support making two planners available in one jar: Resolved
• copy RelDecorrelator & FlinkFilterJoinRule to flink planner to fix CALCITE-3169 & CALCITE-3170: Resolved
• Revert blink changes in DateTimeUtils, and keep it same as flink version.: Resolved
• DateTimeUtils.unixDateCeil returns the same value as unixDateFloor does: Resolved
• RelOptCluster's constructor can not be accessed when connector dependent both flink-planner and blink-planner: Resolved
• Correct package name after relocation: Resolved
• Port csv factories & descriptors from flink-table-planner to flink-csv: Resolved
• ThreadLocalCache clashes for Blink planner: Closed