Yes that did it and thanks. The examples I have seen have shown cases where you can specify values which aren't tokenized but yet do a search against it. Such cases were for something where the name was unique as it is in this case.
Now as I said before some fields have found matches which were not tokenized and some did not. I guess I really need to understand more about Lucene but for the time being I can work with this. Thank you for your help. Matthew Hall-7 wrote: > > Erm.. if its not tokenized that's your problem. > > You are setting up an Analyzer when indexing.. but then not actually > USING it. > > Whereas when you are searching you are running your query through the > analyzer, which transforms your text in such a way that it no longer > matches against your untokenized form. > > So, rerun your index, changing untokenized to tokenized, and I think you > will see the results you are looking for. > > Matt > > samd wrote: >> Oh and the field is not tokenized and stored. >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Luke-shows-in-top-terms-but-no-search-results---tp18638011p18638704.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]
