There is a current limitation in that the code doesn’t actually look into solrconfig.xml for the version. We should fix this, indeed. See
https://github.com/apache/lucene-solr/blob/trunk/solr/contrib/map-reduce/src/java/org/apache/solr/hadoop/TreeMergeOutputFormat.java#L100-101 Wolfgang. On Apr 8, 2014, at 11:49 AM, Dmitry Kan <solrexp...@gmail.com> wrote: > Hello, > > When we instantiate the MapReduceIndexerTool with the collections' conf > directory, we expect, that the Lucene version is respected and the index > gets generated in a format compatible with the defined version. > > This does not seem to happen, however. > > Checking with luke: > > the expected Lucene index format: Lucene 4.0 > the output Lucene index format: Lucene 4.1 > > Can anybody shed some light onto the semantics behind specifying the Lucene > version in this context? Does this have something to do with what version > of solr core is used by the morphline library? > > Thanks, > > Dmitry > > ---------- Forwarded message ---------- > > Dear list, > > We have been generating solr indices with the solr-hadoop contrib module > (SOLR-1301). Our current solr in use is of 4.3.1 version. Is there any tool > that could do the backward conversion, i.e. 4.7->4.3.1? Or is the upgrade > the only way to go? > > -- > Dmitry > Blog: http://dmitrykan.blogspot.com > Twitter: http://twitter.com/dmitrykan > > > > -- > Dmitry > Blog: http://dmitrykan.blogspot.com > Twitter: http://twitter.com/dmitrykan
