Re: Strange index corruption related to numeric fields when upgrading from 6.0.1

2016-09-21 Thread Erick Erickson
; > Regards, > Jan-Willem > > -Original Message- > From: Erick Erickson [mailto:erickerick...@gmail.com] > Sent: Tuesday, September 20, 2016 19:02 > To: java-user > Subject: Re: Strange index corruption related to numeric fields when > upgrading from 6.0.1 >

RE: Strange index corruption related to numeric fields when upgrading from 6.0.1

2016-09-21 Thread Jan-Willem van den Broek
uot; [p]calculon". Thanks for the suggestion though. I'd never even considered that we might be using illegal fieldnames. Regards, Jan-Willem -Original Message- From: Erick Erickson [mailto:erickerick...@gmail.com] Sent: Tuesday, September 20, 2016 19:02 To: java-user Subject: Re

Re: Strange index corruption related to numeric fields when upgrading from 6.0.1

2016-09-20 Thread Erick Erickson
A wild shot in the dark: Are the square brackets really part of the field name? They have never officially been supported, from the Ref Guide: "Field names should consist of alphanumeric or underscore characters only and not start with a digit. This is not currently strictly enforced, but other fi

Strange index corruption related to numeric fields when upgrading from 6.0.1

2016-09-20 Thread Jan-Willem van den Broek
Hi all, I have an application that works fine with 6.0.1, but if I go to 6.1.0 or 6.2.0 then I occasionally get a corrupted index where the SegmentMerger keeps breaking on a numeric field. This is the exception I get: ... (stack of application code) ... Caused by: java.lang.IllegalArgumentExce