Re: Index size and performance degradation

> > If single large index goes beyond GB, It may take more time to merge and > optimize. > This can be achieved w/ a single index too. LogMergePolicy allows setting a maxMergeMB and maxMergeMBForOptimize, which are thresholds that define the largest segment size to be merged. TieredMergePolicy, as

RemoteSearchable deprecated. What to replace it with?

I use a ParallelMultiSearcher to search across a bunch of RemoteSearchables, pretty much as recommended in Lucene In Action, First Edition, with the appropriate adjustments for Lucene 3.0. This seems to be completely deprecated in 3.1. What is the simplest way for me to continue having the ability

Re: Index size and performance degradation

Any one could tthow some light on this? Is it a bad idea to keep multiple shards in a single system? Below are my reasons, Please correct me if iam wrong. 1. If single large index goes beyond GB, It may take more time to merge and optimize. 2. Consider the total size of index is around 10 GB,

Re: Changing Boosting that was set at indexing time

Ok, thanks a lot On 15 June 2011 11:36, Ian Lea wrote: > Don't think so. The boost info is encoded and stored at index time. > > > -- > Ian. > > > On Wed, Jun 15, 2011 at 10:42 AM, liat oren wrote: > > Hi, > > > > I indexed 4 million documents and used boosting factors for each document > at >

Re: Large index merging/optimization?

Waits of several hours on a 4Gb index sounds very unlikely. Are you sure there isn't something else going on that is blocking things? What version of lucene? Decent, error-free, hardware? As for optimize, I'd skip it altogether, or schedule it occasionally when there is no or low activity on the

Re: Boosting a document at query time, based on a field value/range

Hi Thanks for the tip. I tried what you suggested. But, I get the same results as filtering the results on the range of values of a given field, but with different scores now. 1) Here is an example query I gave to Query parser: newtextQuery = textQuery + " OR " + field +":[" + frompercent+ "

Re: Changing Boosting that was set at indexing time

Don't think so. The boost info is encoded and stored at index time. -- Ian. On Wed, Jun 15, 2011 at 10:42 AM, liat oren wrote: > Hi, > > I indexed 4 million documents and used boosting factors for each document at > indexing time. > > I would like to cancel that boosting. Is there a way to do

RE: Merging with writer open on source index?

Yes. - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Shalin Shekhar Mangar [mailto:shalinman...@gmail.com] > Sent: Wednesday, June 15, 2011 1:38 PM > To: java-user@lucene.apache.org > Subject: Merging wi

Large index merging/optimization?

Hi, Our Lucene index grew to about 4 GB . Unfortunately it brought up a performance problem of slow file merging. We have: 1. A writer thread: once an Hour it looks for modified documents, and updates the Lucene index. Usually there are only few modifications, but sometimes we switch the entire co

Merging with writer open on source index?

Hello, IndexWriter.addIndexes(Directory...) method says that the index in each directory must not be changed (opened by a writer) while this method is running. However, IndexWriter.addIndexes(IndexReader...) does not say any such thing. Would I be correct in assuming that since an IndexReader has

Re: Boosting a document at query time, based on a field value/range

Hmm, something went wrong. My mail client swapped dates or displayed your initial question as new :? Threading fail ;) Sorry for this :) On Wed, 2011-06-15 at 12:28 +0200, Elmer wrote: > Let's try again ;) > > If I understand you correctly, you want the returned results to include > all documents

Re: Boosting a document at query time, based on a field value/range

Let's try again ;) If I understand you correctly, you want the returned results to include all documents matching some query, also documents that not satisfy the specified range ("like 20 to 30"), but results that satisfy this range should appear higher in the list. If so, first you have to find

RE: Boosting a document at query time, based on a field value/range

Query q = NumericRangeQuery.newIntRange(...) or Query q = new TermRangeQuery() (depending on your field type) - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Sowmya V.B. [mailto:vbsow...@gmail.com]

Re: Boosting a document at query time, based on a field value/range

On Wed, 2011-06-15 at 11:22 +0200, Sowmya V.B. wrote: > [...] "OR **field**:[20 TO 30]^10" > > Well, my question is partly answered with this clarification. But, I am > still wondering how to do that programmatically. > the (20-30) range is not a fixed range. Its chosen by the user. It can as > we

Changing Boosting that was set at indexing time

Hi, I indexed 4 million documents and used boosting factors for each document at indexing time. I would like to cancel that boosting. Is there a way to do that without re-indexing all of them? Many thanks, Liat

Re: Boosting a document at query time, based on a field value/range

Hi I am not getting the replies to my inbox ...hence the delay in responding. >>I think you misunderstand Eric's answer, as his suggestion does exactly what you ask for. Have you tried the "OR **field**:[20 TO 30]^10" method? Well, my question is partly answered with this clarification. But, I a