Re: merge results from physically separate hosts

2010-05-10 Thread Shaun Senecal
Sorry for the delayed response... Thanks, thats what I thought. In my case, the schema of each index would be slightly different, so I would want to run a PrefixQuery against each index (all fields in each index) using the same query text. Maybe I would be able to take the results from each inde

Re: Class_for_HighFrequencyTerms

2010-05-10 Thread Erick Erickson
Have you looked at TermFreqVector? Best Erick On Mon, May 10, 2010 at 8:10 AM, manjula wijewickrema wrote: > Hi, > > If I index a document (single document) in Lucene, then how can I get the > term frequencies (even the first and second highest occuring terms) of that > document? Is there any cl

Re: MatchAllDocsQuery and MatchNoDocsQuery

2010-05-10 Thread Yonik Seeley
Yes on all counts. Lucene doesn't modify query objects, so they are save for reuse among multiple threads. -Yonik Apache Lucene Eurocon 2010 18-21 May 2010 | Prague 2010/5/10 Mindaugas Žakšauskas : > Hi, > > Can anybody confirm whether MatchAllDocsQuery can be used as an > immutable singletone

MatchAllDocsQuery and MatchNoDocsQuery

2010-05-10 Thread Mindaugas Žakšauskas
Hi, Can anybody confirm whether MatchAllDocsQuery can be used as an immutable singletone? By this I mean creating a single instance and sharing it whenever I need to either use it on its own or in cojunction with other queries put into a BooleanQuery; to result all documents in a search result. Ca

Class_for_HighFrequencyTerms

2010-05-10 Thread manjula wijewickrema
Hi, If I index a document (single document) in Lucene, then how can I get the term frequencies (even the first and second highest occuring terms) of that document? Is there any class/method to do taht? If anybody knows, pls. help me. Thanks Manjula

Re: Trace only exactly matching terms!

2010-05-10 Thread manjula wijewickrema
Hi Anshum & Erick, As you have mentioned, I used SnowballAnalyzer for stemming purposes. It worked nicely. Thnks a lot for your guidence. Manjula. On Fri, May 7, 2010 at 8:27 PM, Erick Erickson wrote: > The other approach is to use a stemmer both at index and query time. > > BTW, it's very easy

Re: The best way to stop indexing quickly?

2010-05-10 Thread Ian Lea
One way would be to identify the most recently added document, save that info somewhere, and close the IndexWriter as normal. Then, when you restart the indexing of the file, skip ahead and start from the last indexed document. Or skip the identify/save bit if your indexing app already has code

The best way to stop indexing quickly?

2010-05-10 Thread alx27 alx27
Hi all, Imagine a situation: Lucene started indexing a huge file, and just after this user demands the application to be shut down immediately. What would be the recommended way of doing this, so that application shuts down within seconds, but with least possible damage to the index? best regards

Re: IndexWriter and memory usage

2010-05-10 Thread Michael McCandless
H... Your usage (searching for old doc & updating it, to add new fields) is fine. But: what memory usage do you see if you open a searcher, and search for all docs, but don't open an IndexWriter? We need to tease apart the IndexReader vs IndexWriter memory usage you are seeing. Also, can yo