CollectionConfiguration contained cache name as a parameter before dynamic cache start was implemented, this parameter was used to specify which cache should be used to store data. Currently CollectionConfiguration does not have cache name; a new cache is dynamically created when necessary according to the configuration passed under the covers.
2015-05-18 14:55 GMT-07:00 tcostasouza <[email protected]>: > Hello there, > > The CollectionConfiguration object passed when creating Queue takes a > cacheName as configuration. If the Queue already receives another name, > what > is there a need for an extra naming parameter? What does it controls? > > Thanks > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Simple-Queue-question-tp326.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
