: The stack trace is attached.  I also saw this warning in the logs not sure

>From your attachment...

 853 SEVERE: org.apache.solr.common.SolrException: undefined field: score
 854   at 
org.apache.solr.handler.component.TermVectorComponent.process(TermVectorComponent.java:142)
 855   at 
org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:194)
 856   at 
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:129)
 857   at org.apache.solr.core.SolrCore.execute(SolrCore.java:1357)

...this is one of the key pieces of info that was missing from your 
earlier email: that you are using the TermVectorComponent.

It's likely that something changed in the TVC on 3x between the two 
versions you were using and thta change freaks out now on "*" or "score" 
in the fl. 

you still haven't given us an example of the full URLs you are using that 
trigger this error. (it's posisble there is something slightly off in your 
syntax - we don't know because you haven't shown us)

All in: this sounds like a newly introduced bug in TVC, please post the 
details into a new Jira issue.

as to the warning you asked about...

: Feb 3, 2011 8:14:10 PM org.apache.solr.core.Config getLuceneVersion
: WARNING: the luceneMatchVersion is not specified, defaulting to LUCENE_24
: emulation. You should at some point declare and reindex to at least 3.0,
: because 2.4 emulation is deprecated and will be removed in 4.0. This parameter
: will be mandatory in 4.0.

if you look at the example configs on the 3x branch it should be 
explained.  it's basically just a new "feature" that lets you specify 
which "quirks" of the underlying lucene code you want (so on upgrading you 
are in control of wether you eliminate old quirks or not)


-Hoss

Reply via email to