thanks erick , A little more information would help here.1> Are you using the same analyzer at both index and query time?
no . sorry , am using StandardAnalyzer at the index time , during querying am using the code snippet found from nabble. 2> Assuming <1> is "yes", did you re-index your data after you created this analyzer? no. 3> What are the results of query.toString()? Looking at that might help you pinpoint what's going on. am getting singular word for all field. 4> Have you examined your index using Luke to see if it has what you *think* it should? yes , i did it , it also returns the same 5> If all of the above doesn't do you any good, I've usually found that writing a small, self-contained test case to illustrate the problem is a great help. Usually, during the course of writing the test case I find the problem. And it's usually in my code <G>. And if it's *not* in my code, a test case provides the Lucene folks with something to work with. sorry , am not clear with this. The analyzer itself looks like it should do what you want on a cursory inspection..... Best Erick -- View this message in context: http://www.nabble.com/singular-and-plural-search-tp25990682p25992140.html Sent from the Lucene - Java Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
