On Wed, May 4, 2016 at 9:12 AM, Alexey Kuznetsov
wrote:
>
> May be, but sending closures is seems as workaround for me.
> This will require from user to write quite a lot of code.
> Just call of loadCache(...some descriptors...) will be much more user
> friendly.
>
I think documenting this prope
Dmitriy,
May be, but sending closures is seems as workaround for me.
This will require from user to write quite a lot of code.
Just call of loadCache(...some descriptors...) will be much more user
friendly.
Also I'm not sure what will happen with key loaded from DB if it will be
not affinity key
Alexey,
What you are saying should already be possible by sending compute closures
to nodes and calling localLoadCache(“myCustomSqlStatement”).
Isn’t it just a case of providing proper example and documentation?
D.
On Tue, May 3, 2016 at 7:22 AM, Alexey Kuznetsov
wrote:
> I totally agree with
I totally agree with Vladimir.
>From JdbcPojo store side we could introduce support of some kind load
descriptor
that will contains SQL to execute and node filter.
On each node store will check node filter and execute SQL if node match the
filter.
This will solve first problem - "do not load fu
Igniters,
We receive more and more questions about the same problem: "I have big a
database. How should I load it to Ignite?"
Obviously, users try to use POJO store as a most convenient approach, but
it cannot handle this case properly.
1) If user invoke *IgniteCache.loadCache()*, then the same r
