lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn Heisey <>
Subject Re: Determining which field caused a document to not be imported
Date Fri, 03 Oct 2014 13:24:23 GMT
On 10/3/2014 5:41 AM, Tom Evans wrote:
> I recently rewrote our SOLR 4.8 dataimport to read from a set of
> denormalised DB tables, in an attempt to increase full indexing speed.
> When I tried it out however, indexing broke telling me that
> "java.lang.Long cannot be cast to java.lang.Integer" (full stack
> below, with the document elided). From googling, this tends to be some
> field that is being selected out as a long, where it should probably
> be cast as a string.
> Unfortunately, our documents have some 400+ fields and over 100
> entities; is there another way to determine which field could not be
> cast from Long to Integer other than disabling each integer field in
> turn?

Can you give us the entire stacktrace, with complete details from any
"caused by" sections?  Also, is this 4.8.0 or 4.8.1?


View raw message