IMO the correct way is to implement generic hints for H2 first and plug Ignite hints there.
Sergi 2017-06-02 17:31 GMT+03:00 Alexey Kuznetsov <[email protected]>: > Hints discussion on H2 user group: > https://groups.google.com/d/topic/h2-database/dHwbBitzXlY/discussion > > On Fri, Jun 2, 2017 at 9:23 PM, Vladimir Ozerov <[email protected]> > wrote: > > > Well, looks like H2 doesn't support hints at the moment, and there is no > > way to add some custom params to SELECT (it is possible for CREATE TABLE > > and CREATE SCHEMA) only. Anyway, this could be nice usability improvement > > for us. > > > > On Fri, Jun 2, 2017 at 5:13 PM, Alexey Kuznetsov <[email protected]> > > wrote: > > > > > I like this, but could you show some examples? > > > > > > On Fri, Jun 2, 2017 at 9:08 PM, Vladimir Ozerov <[email protected]> > > > wrote: > > > > > > > Folks, > > > > > > > > We have quite a few flags on SqlFields and SqlQueryFields classes > which > > > are > > > > used for fine tuning. Probably even more flags will appear soon. > AFAIK > > > > special compatibility mode for Apache Ignite was added to H2 parser > > > > recently. I think we can expose all these flags as SQL hints in the > > query > > > > itself, rather then setting them programmatically (or through > JDBC/ODBC > > > > connection strings). > > > > > > > > Thoughts? > > > > > > > > Vladimir. > > > > > > > > > > > > > > > > -- > > > Alexey Kuznetsov > > > > > > > > > -- > Alexey Kuznetsov >
