Hi,
Thanks for your response, I'm still developing so the schema is still in
flux so I guess that explains it. Oh and regarding the NPE, I updated my
checkout and recompiled and now it's gone so I guess somewhere between
revision 787997 and 798482 it's already been fixed.
Regards,
gwk
Robe
--Original Message-
From: gwk [mailto:g...@eyefi.nl]
Sent: Tuesday, July 28, 2009 3:19 AM
To: solr-user@lucene.apache.org
Subject: Re: debugQuery=true issue
Hi,
Hoping this was completely my fault I changed my solr to a nightly build
from june (I run Solr patched with SOLR-1240) but the sam
Hi,
Hoping this was completely my fault I changed my solr to a nightly build
from june (I run Solr patched with SOLR-1240) but the same problems
occur. After reindexing a single always_on_top document it suddenly
appeared in far down the resultset with score around 5.311 (where it
would be if
Grant Ingersoll wrote:
What's the line number that is giving the NPE? Can you paste in a
stack trace?
Here it is:
java.lang.NullPointerException: value cannot be null
java.lang.RuntimeException: java.lang.NullPointerException: value cannot be null
at org.apache.solr.search.QueryPars
What's the line number that is giving the NPE? Can you paste in a
stack trace?
-Grant
On Jul 27, 2009, at 10:59 AM, gwk wrote:
gwk wrote:
Hi,
I'm playing around with sorting via functionqueries, and I've set
_val_ to the following:
sum(product(always_on_top,5),recip(rord(publication_d
gwk wrote:
Hi,
I'm playing around with sorting via functionqueries, and I've set
_val_ to the following:
sum(product(always_on_top,5),recip(rord(publication_date),1,1000,1000))
Where the field always_on_top is a simple boolean field, where
documents with always_on_top:true should always be
