That's not good. I'll investigate.
On Mon, Nov 25, 2013 at 10:29 PM, Brett Hoerner br...@bretthoerner.com wrote:
Think I got it. For some reason this was in my clusterstate.json after the
upgrade (note that I was using 4.5.X just fine previously...):
router: {
name: compositeId
Hi, I've been using a collection on Solr 4.5.X for a few weeks and just did
an upgrade to 4.6 and am having some issues.
First: this collection is, I guess, implicitly routed. I do this for every
document insert using SolrJ:
document.addField(_route_, shardId)
After upgrading the servers to
Here's my clusterstate.json:
https://gist.github.com/bretthoerner/a8120a8d89c93f773d70
On Mon, Nov 25, 2013 at 10:18 AM, Brett Hoerner br...@bretthoerner.comwrote:
Hi, I've been using a collection on Solr 4.5.X for a few weeks and just
did an upgrade to 4.6 and am having some issues.
Think I got it. For some reason this was in my clusterstate.json after the
upgrade (note that I was using 4.5.X just fine previously...):
router: {
name: compositeId
},
I stopped all my nodes and manually edited this to me implicit (is there
a tool for this? I've always done it
