Generally speaking it is a bad idea to change the schema without
reindexing. I found several little things that could go wrong back
when I had a huge index and could not reindex.
On Wed, Sep 8, 2010 at 4:58 AM, Erick Erickson wrote:
> Ooops, hit send too quickly. Could you show us the entire URL
Ooops, hit send too quickly. Could you show us the entire URL you send
that produces the error?
Erick
On Wed, Sep 8, 2010 at 7:58 AM, Erick Erickson wrote:
> The change in the schema shouldn't matter (emphasis on the should).
>
> What version of SOLR are you using? I tried this query and it work
The change in the schema shouldn't matter (emphasis on the should).
What version of SOLR are you using? I tried this query and it works just
fine for me, I'm using 1.4.1
Best
Erick
On Wed, Sep 8, 2010 at 4:38 AM, Alessandro Benedetti <
benedetti.ale...@gmail.com> wrote:
> My request was very si
My request was very simple:
q= astronomy^0
And Solr returned the exception.
Maybe the zero boost factor is not causing the exception?
1) We indexed n documents with a Schema.xml.
2)Then we changed some field type in the Schema.xml
3)Then we indexed other m documents
Maybe this could cause the exc
On Sep 7, 2010, at 7:08 AM, Alessandro Benedetti wrote:
> Hi all,
> I need to retrieve query-results with a ranking independent from each
> query-result's default lucene score, which means assigning the same score to
> each query result.
> I tried to use a zero boost factor ( ^0 ) to reset to zer
Hi all,
I need to retrieve query-results with a ranking independent from each
query-result's default lucene score, which means assigning the same score to
each query result.
I tried to use a zero boost factor ( ^0 ) to reset to zero each
query-result's score.
This strategy seems to work within the