You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Pim D <pi...@ns.nl> on 2018/01/31 14:06:59 UTC
How to circumvent that a cache store adapter class needs to be on
the classpath of a client node
Whether you have a ATOMIC or TRANSACTIONAL cache, if you would like a client
node to issue a continous query on such a cache, then the client node has to
be able to instantiate the adapter.
To me it is very unlogical that a client needs these classes and the impact
(creating library dependencies to include all CacheStoreAdapters in client
nodes) is very undesirable.
Is there a way to work around this?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Fwd: How to circumvent that a cache store adapter class needs to be
on the classpath of a client node
Posted by Dmitriy Setrakyan <ds...@apache.org>.
Cross posting to dev@.
Igniters, do we really require CacheStoreAdapter on the client side for
non-transactional caches?
D.
---------- Forwarded message ----------
From: Andrey Mashenkov <an...@gmail.com>
Date: Wed, Jan 31, 2018 at 8:34 AM
Subject: Re: How to circumvent that a cache store adapter class needs to be
on the classpath of a client node
To: user@ignite.apache.org
Pim,
This is by design, CacheStore is required on client node for transational
cache,
as node that starts transaction is responsible for update the store.
There is a ticket for this [1].
[1] https://issues.apache.org/jira/browse/IGNITE-1903
On Wed, Jan 31, 2018 at 5:06 PM, Pim D <pi...@ns.nl> wrote:
> Whether you have a ATOMIC or TRANSACTIONAL cache, if you would like a
> client
> node to issue a continous query on such a cache, then the client node has
> to
> be able to instantiate the adapter.
> To me it is very unlogical that a client needs these classes and the impact
> (creating library dependencies to include all CacheStoreAdapters in client
> nodes) is very undesirable.
>
> Is there a way to work around this?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
--
Best regards,
Andrey V. Mashenkov
Re: How to circumvent that a cache store adapter class needs to be on
the classpath of a client node
Posted by Andrey Mashenkov <an...@gmail.com>.
Pim,
This is by design, CacheStore is required on client node for transational
cache,
as node that starts transaction is responsible for update the store.
There is a ticket for this [1].
[1] https://issues.apache.org/jira/browse/IGNITE-1903
On Wed, Jan 31, 2018 at 5:06 PM, Pim D <pi...@ns.nl> wrote:
> Whether you have a ATOMIC or TRANSACTIONAL cache, if you would like a
> client
> node to issue a continous query on such a cache, then the client node has
> to
> be able to instantiate the adapter.
> To me it is very unlogical that a client needs these classes and the impact
> (creating library dependencies to include all CacheStoreAdapters in client
> nodes) is very undesirable.
>
> Is there a way to work around this?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
--
Best regards,
Andrey V. Mashenkov