We have been using version 4.10.4 for quite some time and ran into the
following issue.
Out of the clear blue, one of our clients sees the exception cited below.
We see no prior evidence of anything going awry in our log files. This
literally seems to occur out of nowhere.
Is there any known
> Mike McCandless
>
> http://blog.mikemccandless.com
>
> On Thu, Jul 19, 2018 at 5:54 PM, Stuart Goldberg
> wrote:
>
>> Understood. But I would think that in a tiny program where I add one
>> document and then update it, that the load is so small that it for sur
lse means Lucene does not have to apply all of its
> buffered deletes.
>
> But, it still may have already applied some deletes, so there's no
> guarantee that it won't have applied deletes.
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
> On Thu, Jul 19,
I used NRT readers all the time. I create then with 'applyDeletes' set to
false for performance reasons and take the javadoc at its word that my code
has to be prepared to deal with deleted documents. I thought I understood
that and I wrote my code to be deleted-document-safe.
But I have recently
a-user@lucene.apache.org
Subject: Re: Help! - Max Segment name reached
Hi,
Create a new empty index in a new directory and use addIndex() using the other
directory with the broken index.
This will copy all segments but renumber them.
Uwe
Am April 17, 2018 3:52:27 PM UTC schrieb Stuart Goldberg
&
We have an index that has run into this bug:
https://issues.apache.org/jira/browse/LUCENE-7999
Although this is reported to be fixed in Lucene 7.2, we are at 4.10.4 and
cannot upgrade.
By looking at the code it seems that the last segment number counter is
persisted in segment_h. When
at once rather than large portions of an index.
>
> Le jeu. 1 mars 2018 à 01:20, Stuart Goldberg <sgoldb...@fixflyer.com> a
> écrit :
>
> > I call deleteDocuments
> >
> > On Feb 28, 2018 8:16 PM, "Adrien Grand" <jpou...@gmail.com> wrote:
> >
I call deleteDocuments
On Feb 28, 2018 8:16 PM, "Adrien Grand" <jpou...@gmail.com> wrote:
> What do you mean by purging? What methods do you call?
>
> Le mer. 28 févr. 2018 à 19:34, Stuart Goldberg <sgoldb...@fixflyer.com> a
> écrit :
>
> > I have
I have huge lucene index. On disk it's about 24Gb.
I have a purging routine that is supposed to run and purge old docs.
There are about 650 million docs in there and through testing I have
determined that about 1/3 of these need to be purged.
During the purge, every so often it's
AND DESTROY ANY COPIES.
From: Michael McCandless [mailto:luc...@mikemccandless.com]
Sent: Monday, August 22, 2016 4:38 PM
To: Stuart Goldberg <sgoldb...@fixflyer.com>
Cc: Lucene Users <java-user@lucene.apache.org>
Subject: Re: Problems Refactoring a Lucene Index
The design is i
e a new Document using your application level
information about which fields are tokenized, indexed, etc.
Mike McCandless
http://blog.mikemccandless.com
On Fri, Jul 8, 2016 at 12:12 PM, Stuart Goldberg <sgoldb...@fixflyer.com
<mailto:sgoldb...@fixflyer.com> > wrote:
As o
As our software goes through its lifecycle, we sometimes have to alter
existing Lucene indexes. The way I have done that in the past is to open the
existing index for reading, read each Document, modify it and write that
Document to a new index. At the end of the process, I delete the old index
12 matches
Mail list logo
