CollectionConfiguration.setCacheName()

classic Classic list List threaded Threaded
2 messages Options
alex.glau alex.glau
Reply | Threaded
Open this post in threaded view
|

CollectionConfiguration.setCacheName()

Hi,

Ignite 1.0.0 included method CollectionConfiguration.setCacheName() that disappear in version 1.3.0. What is its replace?

Regards,
Alex
vkulichenko vkulichenko
Reply | Threaded
Open this post in threaded view
|

Re: CollectionConfiguration.setCacheName()

alex.glau wrote
Ignite 1.0.0 included method CollectionConfiguration.setCacheName() that disappear in version 1.3.0. What is its replace?
Hi Alex,

It was removed in favor of dynamic caches. If your queue or set is collocated, it will be stored in a special internal cache. Otherwise, a separate internal cache will be automatically created for each data structure you create.

Actually this change introduced a usability issue for collocated data structures: there is no way to send a closure to a particular queue/set because user is unaware of the system cache it's stored in. We already have a ticket for this: https://issues.apache.org/jira/browse/IGNITE-1144

Are you using closure collocation?

-Val