Hi Jeff,
CacheStore class should be in classpath on all nodes including clients.
1 нояб. 2017 г. 4:52 пользователь "Jeff Jiao"
написал:
> Hi Andrew,
>
> Thanks a lot for all the replies.
>
> yes BoConverter implements Serializable, or Ignite will throw
> NotSerializableException.
> The "Class"
Hi Andrew,
Thanks a lot for all the replies.
yes BoConverter implements Serializable, or Ignite will throw
NotSerializableException.
The "Class" here is actually for hibernate to get data from DB:
org.hibernate.Session.get(Class clazz, Serializable id).
After getting the data, BoConverter convert
Hi Jeff,
Is BoConverter object serializable and is class present on all nodes?
You store configured with storeKeepBinary true, so store will receive
binary objects.
Why you need value class here? Binary object concept is to overcome a
requirement to have all value classes on server side.
On Tu
my factory is very easy, just override the create method and set attributes,
please see the code below.
In the cache store i use hibernate to get data from Oracle and convert it to
binaryObject and then put into Ignite, so I make people can config their own
converter and class.
Thanks.
import ja
Hi Jeff,
Looks weird.
Can you share a StoreFactory code and cache config?
Is factory stateless? Or may be there is smth else not stateless in cache
configuration that is missed in log?
On Fri, Oct 27, 2017 at 10:50 AM, Jeff Jiao
wrote:
> hi guys,
>
> can anyone give some advice...
> what can y
hi guys,
can anyone give some advice...
what can you see from this exception server side log when client connect to
it:
Caused by: java.io.NotSerializableException:
org.apache.ignite.internal.processors.cache.binary.IgniteBinaryImpl
why it says IgniteBinaryImpl is not serializable?
--
Sent fro
just in case you don't see my replies, I will put all of these in one msg.
yes, PIgniteCacheStoreFactory implements javax.cache.configuration.Factory,
and this factory extends Serializable.
like I said " I already created my own factory to create the cache store to
avoid Serialization problem."
ok I tried to comment out this part, the exception I saw on server node
before doesn't appear this time...
so it looks like Cache Factory/Store problem... but why...
yes, PIgniteCacheStoreFactory implements javax.cache.configuration.Factory,
and this factory extends Serializable.
like I said " I already created my own factory to create the cache store to
avoid Serialization problem." without the custom factory, it cannot start
any nodes b/c my own cacheStore do
Hi,
Looks like node fails while trying to serialize cache configuration.
Would you please check if com.pingan.pilot.cache.impl.ignite.
PIgniteCacheStoreFactory implements Serializable?
On Wed, Oct 25, 2017 at 10:12 AM, Jeff Jiao
wrote:
> Hi Ignite Community,
>
> I have a Ignite server node run
Hi Ignite Community,
I have a Ignite server node running well, it has a cache store connect to
Oracle, and here I already created my own factory to create the cache store
to avoid Serialization problem. The server node suppose to store
BinaryObject as value. I already tested all the get, put, remo
11 matches
Mail list logo
