Dmitriy, I don't believe that EMR does include Solr or Lucene in their EMR AMIs. But there was a recent AMI update that ruined some things for us. Have you tried using an older AMI?
One headache for us has been that the EMR AMI uses an older version of Apache HttpComponents than that of Solr 4.3, and they're not compatible. So we're having to use an older SolrJ to compensate. I haven't had problems with conflicting Lucene deps in EMR, however. Michael Della Bitta Applications Developer o: +1 646 532 3062 | c: +1 917 477 7906 appinions inc. “The Science of Influence Marketing” 18 East 41st Street New York, NY 10017 t: @appinions <https://twitter.com/Appinions> | g+: plus.google.com/appinions<https://plus.google.com/u/0/b/112002776285509593336/112002776285509593336/posts> w: appinions.com <http://www.appinions.com/> On Sun, Aug 11, 2013 at 2:05 PM, Dmitriy Shvadskiy <dshvads...@gmail.com>wrote: > Erick, > > Thank you for the reply. Cloudera image includes Solr 4.3. I'm not sure > what > version Amazon EMR includes. We are not directly referencing or using their > version of Solr but instead build our jar against Solr 4.4 and include all > dependencies in our jar file. Also error occurs not while reading existing > index but simply creating an instance of EmbeddedSolrServer. I think there > is a conflict between jars that EMR process loads and that our map/reduce > job requires but I can't figure out what it is. > > Dmitriy > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Problem-running-Solr-indexing-in-Amazon-EMR-tp4083636p4083855.html > Sent from the Solr - User mailing list archive at Nabble.com. >
