Fluffy, Cache is created only once and with only one version of config (it can be taken declared in XML or in code - doesn't matter). And in case there is a cache configuration in initial Ignite config, it will be created on node startup, so all other attempts to create a cache with the same name dynamically after node is already started will fail. In case you use getOrCreateCache method with modified configuration, it will get existing cache instead of creating a new one, therefore this configuration will be ignored.
-Val On Sat, Jun 13, 2015 at 4:59 AM, fluffy <[email protected]> wrote: > Val, > > never mind, I think that did it. I had to make a couple of other changes in > my environment, but that I think allowed indexing to work again. > > I never realized that the Spring XML definition and the java DSL of a Cache > are mutually exclusive? From GridGain I was used to specifying the basics > in > Spring XML and then just modifying it in Java when necessary.... > > The documentation says that XMl and Java are mutually exclusive for the > Index MetaData stuff, but in terms of CacheConfiguration, does it pick a > Spring XML configuration over a Java configuration and then ignore Java? > > Thanks much > > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Trouble-Enabling-Query-Indexing-tp377p490.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
