Hello!
MutableConfiguration does not include cache name so it is not used when
computing hash code.
Since this is an implementation detail that is never documented I think it
is a very minor issue from our side. Still, you can fill an issue against
Apache Ignite JIRA if you like.
Regards,
I
As I pass different cache name as the parameter, so I suppose the hash code
should be different.
in my use case i create Spring bean via @Bean with @Scope(value =
SCOPE_PROTOTYPE)
when I try to verify if a new instance is created or not I found the hash
code is the same.
that's why I ask
Hello!
hashCode is implemented by MutableConfiguration (from JCache) which only
takes a subset of fields into account.
Why is this a problem for you?
Regards,
--
Ilya Kasnacheev
ср, 19 сент. 2018 г. в 10:21, kcheng.mvp :
> here is a simple test code
>
> CacheConfiguration cacheCfg = new
here is a simple test code
CacheConfiguration cacheCfg = new CacheConfiguration<>(IG_P);
cacheCfg.setBackups(1);
cacheCfg.setWriteSynchronizationMode(CacheWriteSynchronizationMode.PRIMARY_SYNC);
logger.info("instance {}", cacheCfg.hashCode());
cacheCfg = new
