+1 (non-binding) One question about H2's future. Once Calcite is the default, what is the plan for the H2 engine?
Without a plan, I'm afraid we'll end up supporting both engines indefinitely. Every bug fix and SQL change has to be checked against both of them, and H2 itself stays pinned at 1.4.197. Also, as long as H2 remains a fully supported option, many users will simply set it back as their default and never move. I'd propose deprecating the H2 engine in 2.20. That gives users one release to try Calcite as the default and report problems. Then we can agree on what has to be true before H2 can be removed. On Wed, 7 Oct 2026 at 9:02 PM, Maxim Muzafarov <[email protected]> wrote: > +1 > > On Wed, 7 Oct 2026 at 19:51, Kirill Tkalenko <[email protected]> wrote: > > > > +1 >
