It is possible that in the future Calcite will change the way to initialize its plannerImpl. But I doubt when that happens, even the current `Frameworks.getPlanner(config)` will be changed, so Beam will likely to change the API call at that moment.
Right now since we are using calcite-core 1.17.0, and the signature of constructor is guaranteed to be stable. When we upgrade calcite dependency, we can change in Beam if Calcite changes its plannerImpl's constructor signature. [ Full content available at: https://github.com/apache/beam/pull/6598 ] This message was relayed via gitbox.apache.org for devnull@infra.apache.org