[CALCITE-3069] Make the JDBC Connection more extensible like the FrameworkConfig API

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.19.0
• Component/s: core
• Assignee: Unassigned
• Reporter: Lai Zhou
• Created: 15/May/19 10:48
• Updated: 16/May/19 18:13

Description

More and more users are interested in building custom sql engines on top of Calcite.

But for different sql engines, there're differences on sql parsing, expression conversions, implicit type casting ...even the physical implementations for logical plan. 

I think the FrameworkConfig API now provided a better way than JDBC Connection to custom these things.Are there any plans  in the roadmap to enhance the JDBC Connection config , like FrameworkConfig API , to improve Calcite's extensibility ?

Otherwise, implementing the whole physical plan like the default Enumerable-implementation will be boring , that also require a lot of work. May be we can do something to make the physical and execution plan(that says code-gen ) more customizable.

Are there any thoughts on this issue?