I have a patch implementing a new test: https://dl.dropboxusercontent.com/u/97770508/testoptimizeonecore.patch
I suspect that sending an optimize command to a SolrCloud core will *not* limit itself to just that core if distrib is set to false, so I am trying to test for this, as I cannot easily set up a test cloud with Solr 4.6.1. I know for sure that this is the behavior on 4.2.1, because I have tested it on a production SolrCloud system. In writing the test, what I've found is that somehow the collection is getting optimized even though I have not yet asked it to optimize anything. I have looked through the code that I am extending and I cannot figure out why it's being optimized or how to turn it off. There's a nocommit in the code mentioning what has to happen once the immediate problem gets fixed. Can anyone point me in the right directionto making this work right? Should I extend a different base class? Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
