[FLINK-21045] Improve Usability of Pluggable Modules

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.13.0
• Fix Version/s: 1.13.0
• Component/s: Table SQL / Planner
• Assignee: Jane Chan
• Reporter: Nicholas Jiang
• Created: 20/Jan/21 06:01
• Updated: 23/Mar/21 13:44
• Resolved: 23/Mar/21 07:33

Description

This improvement aims to

1. Simplify the module discovery mapping by module name. This will encourage users to create singleton of module instances.
2. Support changing the resolution order of modules in a flexible manner. This will introduce two methods #useModules and #listFullModules in both ModuleManager and TableEnvironment.
3. Support SQL syntax upon LOAD/UNLOAD MODULE, USE MODULES, and SHOW [FULL] MODULES in both FlinkSqlParserImpl and SqlClient.
4. Update the documentation to keep users informed of this improvement.

Please reach to the discussion thread for more details.

Issue Links

• Blocked: FLINK-21849 'SHOW MODULES' tests for CliClientITCase lack the default module test case
• relates to: FLINK-14132 Extend core table system with pluggable modules

Sub-Tasks

• Support 'useModules' and 'listFullModules' in ModuleManager and TableEnvironment: Closed
• Use module name to perform module factory discovery: Closed
• Support 'LOAD/UNLOAD MODULE' syntax: Closed
• Support 'USE MODULES' syntax: Closed
• Support 'SHOW [FULL] MODULES' syntax: Closed
• Update module documentation: Closed
• Support 'useModules' and 'listFullModules' in PyFlink: Closed
• Migrate module-related tests in LocalExecutorITCase to new integration test framework: Closed