ries are now growing typically from a few
hundred kilobytes to a few megabytes each, after extensive editing.
One issue that appeared is when the parent IndexWriter's configured
merge policy selects segments for merging from the shared part of two
branches; these segments cannot be deleted by the Index
gt; From: luc...@mikemccandless.com
> Date: Thu, 2 May 2013 06:57:06 -0400
> Subject: Re: Merge policy!
> To: java-user@lucene.apache.org
>
> I don't think those APIs changed from 4.1 to 4.2.1?
>
> Can you give more details? Eg, which merge policy you ar
I don't think those APIs changed from 4.1 to 4.2.1?
Can you give more details? Eg, which merge policy you are using?
Mike McCandless
http://blog.mikemccandless.com
On Thu, May 2, 2013 at 6:53 AM, andi rexha wrote:
> Hi,
> I want to create a simulation of the old "optimize&
Hi,
I want to create a simulation of the old "optimize" for an index. I can do it
for 4.1 api, because I can use the method "setUseCompoundFile(true)" for the
merge policy and call indexWriter.forceMerge(1);
But I dont find a way to do it for the 4.2.1 api. Do you have an
Have you considered having fewer indexes, each storing data for
multiple users? Obviously with some indexed field that you can use
for restricting searches to data for that user.
I believe that is more common practice for this sort of scenario and
is known to work well. You seem to be adding pos
Thank you, Ian
I have a large number of dynamically changing Index, so calling
expungeDeletes() and optimize() is very costly.
At this point I am opting to just set a optimum merge factor and skip
optimize()
On Tue, Oct 5, 2010 at 2:54 PM, Ian Lea wrote:
> Deleted docs will be removed by lucene
Deleted docs will be removed by lucene at some point - there is no
need to run optimize.
Read the javadocs for IndexWriter for details. See also
expungeDeletes(). That may be just what you need.
--
Ian.
On Tue, Oct 5, 2010 at 7:48 AM, Naveen Kumar wrote:
> Hi
> I have one more question, does
Hi
I have one more question, does Lucene purge the deleted documents before
merging the segments, or purging of deleted documents done only when
optimized?
On Thu, Sep 30, 2010 at 4:59 PM, Naveen Kumar wrote:
> Hi
> I have a Very large number (say 3 million) of frequently changing Small
> index
Hi
I have a Very large number (say 3 million) of frequently changing Small
indexes. 90% of these indexes contain about 50 documents, while a few 2-3%
indexes have about 100,000 documents each (these being the more frequently
used indexes).
Each index belongs to a signed in user, thus can have unpre
