Sounds like a question better asked in one of the Cloudera support forums, 'cause all I can do is guess ;).
I suppose, theoretically, that you could check out the Solr5 code and substitute the httpclient-4.2.5.jar in the build system, recompile and go, but that's totally a guess based on zero knowledge of whether compiling Solr with an earlier httpclient would even work. Frankly, though, that sounds like more work than distributing the older jar to the data nodes. Best, Erick On Tue, Jun 16, 2015 at 7:23 AM, adfel70 <adfe...@gmail.com> wrote: > Hi, > > We recently started testing solr 5, our indexer creates mapreduce job that > uses solrj5 to index documents to our SolrCloud. Until now, we used solr > 4.10.3 with solrj 4.8.0. Our hadoop dist is cloudera 5. > > The problem is, solrj5 is using httpclient-4.3.1 while hadoop is installed > with httpclient-4.2.5 > and that causing us jar-hell because hadoop jars are being loaded first and > solrj is using closeablehttpclient class which is in 4.3.1 but not in 4.2.5 > > Does anyone encounter that? and have a solution? or a workaround? > > Right now we are replacing the jar physically in each data node > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/mapreduce-job-using-soirj-5-tp4212199.html > Sent from the Solr - User mailing list archive at Nabble.com.
