Thanks Otis,
I'll give that a try.
Jed.
On 02/06/2011 08:06 PM, Otis Gospodnetic wrote:
Yup, here it is, warning about needing to reindex:
http://twitter.com/#!/lucene/status/28694113180192768
Otis
----
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
Lucene ecosystem search :: http://search-lucene.com/
----- Original Message ----
From: Erick Erickson<erickerick...@gmail.com>
To: solr-user@lucene.apache.org
Sent: Sun, February 6, 2011 9:43:00 AM
Subject: Re: HTTP ERROR 400 undefined field: *
I *think* that there was a post a while ago saying that if you were
using trunk 3_x one of the recent changes required re-indexing, but don't
quote me on that.
Have you tried that?
Best
Erick
On Fri, Feb 4, 2011 at 2:04 PM, Jed Glazner
<jglaz...@beyondoblivion.com>wrote:
Sorry for the lack of details.
It's all clear in my head.. :)
We checked out the head revision from the 3.x branch a few weeks ago (
https://svn.apache.org/repos/asf/lucene/dev/branches/branch_3x/). We
picked up r1058326.
We upgraded from a previous checkout (r960098). I am using our customized
schema.xml and the solrconfig.xml from the old revision with the new
checkout.
After upgrading I just copied the data folders from each core into the new
checkout (hoping I wouldn't have to re-index the content, as this takes
days). Everything seems to work fine, except that now I can't get the
score
to return.
The stack trace is attached. I also saw this warning in the logs not sure
exactly what it's talking 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.
Here is my request handler, the actual fields here are different than what
is in mine, but I'm a little uncomfortable publishing how our companies
search service works to the world:
<requestHandler name="standard" class="solr.SearchHandler" default="true">
<lst name="defaults">
<str name="echoParams">explicit</str>
<str name="defType">edismax</str>
<bool name="tv">true</bool>
<!-- standard field to query on -->
<str name="qf">field_a^2 field_b^2 field_c^4</str>
<!-- automatic phrase boosting! -->
<str name="pf">field_d^10</str>
<!-- boost function -->
<!--
we'll comment this out for now becuase we're passing it to
solr as a paramter.
Once we finalize the exact function we should move it here
and take it out of the
query string.
-->
<!--<str name="bf">log(linear(field_e,0.001,1))^10</str>-->
<str name="tie">0.1</str>
</lst>
<arr name="last-components">
<str>tvComponent</str>
</arr>
</requestHandler>
Anyway Hopefully this is enough info, let me know if you need more.
Jed.
On 02/03/2011 10:29 PM, Chris Hostetter wrote:
: I was working on an checkout of the 3.x branch from about 6 months ago.
: Everything was working pretty well, but we decided that we should update
and
: get what was at the head. However after upgrading, I am now getting
this
FWIW: please be specific. "head" of what? the 3x branch? or trunk? what
revision in svn does that corrispond to? (the "svnversion" command will
tell you)
: HTTP ERROR 400 undefined field: *
:
: If I clear the fl parameter (default is set to *, score) then it works
fine
: with one big problem, no score data. If I try and set fl=score I get
the same
: error except it says undefined field: score?!
:
: This works great in the older version, what changed? I've googled for
about
: an hour now and I can't seem to find anything.
i can't reproduce this using either trunk (r1067044) or 3x (r1067045)
all of these queries work just fine...
http://localhost:8983/solr/select/?q=*
http://localhost:8983/solr/select/?q=solr&fl=*,score
http://localhost:8983/solr/select/?q=solr&fl=score
http://localhost:8983/solr/select/?q=solr
...you'll have to proivde us with a *lot* more details to help understand
why you might be getting an error (like: what your configs look like,
what
the request looks like, what the full stack trace of your error is in the
logs, etc...)
-Hoss
