lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alan Miller <alan.mill...@gmail.com>
Subject Re: debugging failed documents
Date Fri, 09 Dec 2011 14:09:53 GMT
Thanks Cody,

I forgot that had I redirected my logs to webapps/solr/log/solr.log

The error there was clear enough for me. The output of my DIH query
contained some string values and my schema was trying to read the
field as an integer.

I though I had to set the field type to integer to be able to do do range
queries like "total_mem:[  16383 TO 32769 ]".  If my DB doesn't have
valid data for a host's total_mem it shows 'unknown'.

I changed the field type to text_general and the range queries still work
so (for now) the problem seems resolved.

Thanks,
Alan



On Tue, Dec 6, 2011 at 11:40 PM, Young, Cody <Cody.Young@move.com> wrote:

> In my experience with DIH, the errors for failed documents end up in the
> log files. Catalina.out for Tomcat.
>
> Can you check your log files?
>
> Cody
>
> -----Original Message-----
> From: Alan Miller [mailto:alan.miller3@gmail.com]
> Sent: Tuesday, December 06, 2011 1:25 PM
> To: Solr
> Subject: debugging failed documents
>
> Just getting started with DIH and I have a very simple setup.
>
> My dih-config.xml is querying my postgres db and does a select on a
> crosstab() table that returns just 100 rows.
>
> When i do a full-import i see that 22 docs fail but what debug settings
> do i have to tweak to see why the docs failed?
>
> When I run the same query manually I see all 100 rows. The  22 rows
> missing in my index look good in the manual output.
>
> Alan
>
>
> Sent from my iPhone
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message