: by upload the configuration information to ZooKeeper. The newest index : needs the UIMA jars. Normally I would put them in the core's /lib : directory, but since I am only accessing my server via ZooKeeper, I : don't have that directory as an option. : : I know I could manually upload the jars onto the server, and then put : some sort of path to them, but I'm hoping to manage all uploading of : core specific configurations (and jars) via ZooKeeper. I'm wondering if
i would use one or more explicit <lib ... /> directives in your solrconfig.xml file, pointing at absolute paths where you consistently upload these jars on every machine (or better still: use sharedLib in solr.xml) rather then the implicit ./lib per core. that way no matter how many collections you create on these machines (or how many solr instances), the configs can all point to a single uniform place on the machine to find these jars instead of needing ot copy them arround. yes: you still have to upload them to the machines yourself, but you also have to upload solr to these machines yourself -- code needs deployed, even if it's a plugin. >> ... maybe I just need to tweak my <lib/> definitions in my >> solrconfig.xml to look for all the places that Jars may exist, even >> though on my local box it's different then on my integration Solr box. doesn't sound very cloud-ish to have diff stuff installed in diff places on diff machines ... but you could use a system property to specify the basepath for all your libs and then override it on your dev machine. -Hoss
