lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ranjit Kumar <Ranjit.Ku...@otssolutions.com>
Subject lucene3.0.2: getting incorrect no. of occurrence in file
Date Mon, 06 Dec 2010 12:55:45 GMT
Hi,
I am facing same problem with lucen3.0.2  search. I am using StandardAnalyzer to create index.
IndexWriter writer = new IndexWriter(FSDirectory.open(INDEX_DIR), new StandardAnalyzer(Version.LUCENE_CURRENT),
true, new IndexWriter.MaxFieldLength(1000000));
on the other hand for search I am using same analyser. In case of term query(ie; query having
single word) result is fine and gives correct no of occurrence in the file searched.
When using  phrase query (ie;  multiTerm query like sql server) it gives file that contents
 sql server (no. of docoments) but do not gives correct no of occurrence in each document.
If you have any solution plz.. help me out.


Thanks & Regards,
Ranjit Kumar
Associate Software Engineer

[cid:image002.jpg@01CB7089.C0069B40]

US:       +1 408.540.0001
UK:       +44 208.099.1660
India:   +91 124.474.8100 | +91 124.410.1350
FAX:     +1 408.516.9050
http://www.otssolutions.com

===================================================================================================
Private, Confidential and Privileged. This e-mail and any files and attachments transmitted
with it are confidential and/or privileged. They are intended solely for the use of the intended
recipient. The content of this e-mail and any file or attachment transmitted with it may have
been changed or altered without the consent of the author. If you are not the intended recipient,
please note that any review, dissemination, disclosure, alteration, printing, circulation
or Transmission of this e-mail and/or any file or attachment transmitted with it, is prohibited
and may be unlawful. If you have received this e-mail or any file or attachment transmitted
with it in error please notify OTS Solutions at info@otssolutions.com ===================================================================================================

Mime
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message