Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <20013818.post@talk.nabble.com>
Date: Thu, 16 Oct 2008 06:31:31 -0700 (PDT)
From: "Karsten F." <karsten-lucene@fiz-technik.de>
To: java-user@lucene.apache.org
Subject: Re: No hits for longer search strings
In-Reply-To: <11e852b50810160314o395e0aaoa9602f0439b18e4d@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <11e852b50810160314o395e0aaoa9602f0439b18e4d@mail.gmail.com>


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: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org