/
- Original Message
> From: dan whelan
> To: solr-user@lucene.apache.org
> Sent: Fri, June 3, 2011 4:34:40 PM
> Subject: Re: fq null pointer exception
>
> It returned results when I added the fl param.
>
> Strange... wonder what is going on there
>
> Thanks,
>
&g
Dan, this doesn't really have anything to do with your filter on the
Status field except that it causes different documents to be selected.
The root cause is a schema mismatch with your index.
A string field (or so the schema is saying it's a string field) is
returning "null" for a value, which is
arch-lucene.com/
- Original Message
From: dan whelan
To: solr-user@lucene.apache.org
Sent: Fri, June 3, 2011 1:38:33 PM
Subject: Re: fq null pointer exception
Otis, I just deleted the documents and committed and I still get that error.
Thanks,
Dan
On 6/3/11 9:43 AM, Otis Gospodn
Subject: Re: fq null pointer exception
>
> Otis, I just deleted the documents and committed and I still get that error.
>
> Thanks,
>
> Dan
>
>
> On 6/3/11 9:43 AM, Otis Gospodnetic wrote:
> > Dan, does the problem go away if you get rid of those 112 documen
Otis, I just deleted the documents and committed and I still get that error.
Thanks,
Dan
On 6/3/11 9:43 AM, Otis Gospodnetic wrote:
Dan, does the problem go away if you get rid of those 112 documents with empty
Status or replace their empty status value with, say, "Unknown"?
Otis
Semate
Dan, does the problem go away if you get rid of those 112 documents with empty
Status or replace their empty status value with, say, "Unknown"?
Otis
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
Lucene ecosystem search :: http://search-lucene.com/
- Original Message
>
