Hi Chris, most likely this is not a lucene problem.
You looked with luke in the stored fields of your document? Please take a second look with luke in the terms of your field 'unique_id' (with "Show top terms"): What do you see? Best regards Karsten btw: why do you use the prefix search? This could also be reason for problem, because your QueryParser could possible have extra rules to handle prefixQueries. Chris Mannion-2 wrote: > > Hi All > > I have a bit of a puzzle in the Lucene system we've been running. Part of > our use involves inserting documents indexed by a unique key and then > running exact searches to find that single document again later to display > (the documents are also indexed by several other fields and used in a > broader search, hence using Lucene). I've just hit a strange bug lately > where the documents are not being found under certain circumstances. > We've > usually been indexing by unique ids about 12 characters in length, e.g. > t10001c53421 and this has always worked fine, however when the id length > is > whacked up to 18, e.g. t10001c63241985103, the search never finds the > documents. I've used Luke which allows me to open the index for browsing > and can see that the documents are definitely in the index and have the > correct unique id values stored in there, so it seems to be a problem with > the search. > > We're using a search string like (unique_id:(t10001c63241985103*) ) and > standard analyzers to run the search. Does anyone have any ideas why the > increased search string length would affect things like this? > > -- > Chris Mannion > iCasework and LocalAlert implementation team > 0208 144 4416 > > -- View this message in context: http://www.nabble.com/No-hits-for-longer-search-strings-tp20010839p20013818.html Sent from the Lucene - Java Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
