Thank you very much for answer.
You were right. There was no luceneMatchVersion in solrconfig.xml of our dev
core. We thought that values not present in core configuration are copied
from main solrconfig.xml. I will investigate if our administrators did
something wrong during upgrade to 3.1.
On T
Thank you very much for answer.
You were right. There was no luceneMatchVersion in solrconfig.xml of our dev
core. We thought that values not present in core configuration are copied
from main solrconfig.xml. I will investigate if our administrators did
something wrong during upgrade to 3.1.
On T
What do you have in solrconfig.xml for luceneMatchVersion?
If you don't set this, then its going to default to "Lucene 2.9"
emulation so that old solr 1.4 configs work the same way. I tried your
example and it worked fine here, and I'm guessing this is probably
whats happening.
the default in the
