Igniters. We have deprecated the 2019 SqlQuery class. SqlQuery is not supported in the Calcite module.
So, after the default switch SqlQuery will not be supported on the default Ignite layout. Maybe it's time to remove them completely? ср, 7 окт. 2026 г. в 22:48, Nikolay Izhikov <[email protected]>: > > Hello, Maxim. > > > One question about H2's future. Once Calcite is the default, what is the > > plan for the H2 engine? > > I think we have to do the following: > > 1. Provide ignite-indexing in Ignite distro as backup while catching > calcite issues in the wild. > 2. Move ignite-indexing to extensions. > 3. Remove (or just keep as is) ignite-indexing without any updates or > support in extension repo. > > > ср, 7 окт. 2026 г. в 22:29, Максим Михайлович Давыдов > <[email protected]>: > > > > +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 > > >
