It sounds like you were somehow getting the old jar file
rather than the new one. It _should_ have worked to just
drop the new jar file in the directory, assuming you'd
removed all traces of the old jar file...
But if you have it working now, that's what counts.
FWIW,
Erick
On Tue, Jun 14, 2016
Actually my changes in updateProcessor.0.1.jar were not reflecting
(functionality wise). I was getting no errors.
Well I dropped the jar file in shared folder only updateProcessor.0.1.jar .
The entry added in solrconfig file was
**
In /updateProcessor.0.1.jar/ I had class file with the path
/org
First, having 5 Zookeeper nodes to manage 4 Solr nodes
is serious overkill. Three should be more than sufficient.
what did you put in your configuration? Does your
directive in solrconfig.xml mention updateProcessor.0.1?
And what error are you seeing exactly?
When Solr starts up, part of the vo
I have Solr cloud configuration which we run on 4 servers. We use tomcat as
web server for solr. I have 5 zookeepers to maintain the data-replication. I
have added a jar file with custom update processor. This is in shared folder
which is mention in solr.xml**While creating the first version of thi
