Hello! Unfortunately it does not seem to me that this implementation is robust enough. If you compare it with org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore#loadCache you will see that it lacks pooling, support for args, etc.
However, CacheJdbcBlobStore is not an internal class. You can surely extend/subclass it in your code, and then instantiate the extended version where you have your own loadCache. This is what I recommend, instead of waiting for a "generic" loadCache in Ignite code. Regards, -- Ilya Kasnacheev вс, 24 нояб. 2019 г. в 11:09, Кузин Никита (Nikita Kuzin) < [email protected]>: > also I found the issue: https://issues.apache.org/jira/browse/IGNITE-12078 > with attached PR: https://github.com/apache/ignite/pull/6783 > > so it seems to be done (merged) very easy:) > > _________________________________ > С уважением, Никита Кузин > Ведущий программист-разработчик > > * Интернейшнл АйТи Дистрибьюшн* > > e-mail: [email protected] > тел.: 84995021375 доб. 320 > моб. тел.: 79260948887 > 115114, Москва, Дербеневская ул., 20-27 > ------------------------------ > *От:* Кузин Никита (Nikita Kuzin) > *Отправлено:* 23 ноября 2019 г. 21:22 > *Кому:* [email protected] <[email protected]> > *Тема:* Load cache from 3rd party persistence > > Hello! > > We want to use CacheJdbcBlobStore and everything seems fine, but it have > empty implementation of loadCache method since it extends CacheStoreAdapter > with empty implementation of loadCache. > How we can deal with it? Why CacheJdbcBlobStore doesn't implement this > method? > > _________________________________ > С уважением, Никита Кузин > Ведущий программист-разработчик > > * Интернейшнл АйТи Дистрибьюшн* > > e-mail: [email protected] > тел.: 84995021375 доб. 320 > моб. тел.: 79260948887 > 115114, Москва, Дербеневская ул., 20-27 >
