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" for an index. I ca
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
