Николай, It looks a little bit hacky to me. I believe SQL drivers usually use that approach as a workaround because there is no other common way to do that.
Sure we can recommend users to use cache.size() or anything other similar way to ensure the connection is alive, but it still looks like a workaround to me. Best Regards, Igor On Sun, Sep 13, 2020 at 10:16 PM Николай Ижиков <nizhi...@apache.org> wrote: > Hello, Pavel. > > SQL drivers usually use “SELECT 1” query to ensure connection is alive. > > Can we use similar approach? > > Отправлено с iPhone > > > 13 сент. 2020 г., в 13:26, Pavel Tupitsyn <ptupit...@apache.org> > написал(а): > > > > Igniters, > > > > There is a feature request for a thin client Ping operation on the user > > list [1]. > > I think that is a good idea - IgniteClient.ping() will be a valuable > > addition. > > > > Any objections? > > > > [1] > > > http://apache-ignite-users.70518.x6.nabble.com/Feature-request-method-to-test-active-connection-in-Ignite-thin-client-td33985.html >
