able
to identify (and hopefully fix) conflicts at build-time.
Thanks,
Stan
From: chuston
Sent: 18 мая 2018 г. 4:04
To: user@ignite.apache.org
Subject: Re: Ignite equivalent of @GridUserResource
I'm also reviving a mothballed GridGain system that used a @GridUserResource
- moving from Java 6/Gri
I'm also reviving a mothballed GridGain system that used a @GridUserResource
- moving from Java 6/GridGain 3 to Java 1.8 / Ignite 2.4.0+
To replace it, I'm doing the following:
- Use a LifeCycleBean that populates the nodeLocalMap before startup.
- the objects placed in the nodeLocalMap are
I will try that.
Thanks,
Paolo
On Wed, Sep 30, 2015 at 2:39 AM, vkulichenko
wrote:
> Hi Paolo,
>
> You can use node local map instead [1]. It's a per-node singleton storage
> that has standard ConcurrentMap API and can be used for any user resources
> (e.g., JDBC connections, pools, etc). You
Hi Paolo,
You can use node local map instead [1]. It's a per-node singleton storage
that has standard ConcurrentMap API and can be used for any user resources
(e.g., JDBC connections, pools, etc). You can inject Ignite instance to your
job using @IgniteInstanceResource annotation and acquire the m
