I'm not sure, but based on what I saw in the script command line, I would expect ONLY otac_en to show up - since that is the only one mentioned on the -confname flag...
Glad you've made some progress - happy to try to assist in figuring out the larger problem if you want to. I have sweat a lot of blood on trying to figure out how to upgrade, so it may be that I'll have some useful insights... Or not.. <grin> you never know... Depends on how similar our use cases are I suppose... On Fri, Sep 9, 2016 at 3:41 PM, igiguere <igigu...@opentext.com> wrote: > Hi again; > > To answer your questions: > > 1. I use a ZK browser, so I can see what happens in ZK. > https://github.com/DeemOpen/zkui > > 2. Solr 4.3 is on it's own ZK, on one server. Solr 5.4 is on another ZK, > on > a different server. No mixing whatsoever. > > 3. Take <ZK> to mean "ZK root", so, yes /ot is at the root > > Meanwhile, I have made some "progress", if that's what I could call it. By > deleting form ZK all the irrelevant configurations, and leaving only > "otac_en", I was able to migrate one collection. > > Fortunately, for this specific project, only "otac_en" is relevant, so we > could live with the deletion of the other configs. > However, we can't expect ZK to only ever hold just one config for Solr. > > > > > > -- > View this message in context: http://lucene.472066.n3. > nabble.com/Migrating-config-found-but-not-mapped-to- > collection-tp4295375p4295391.html > Sent from the Solr - User mailing list archive at Nabble.com. >
