[#LUCENE-16] The 'in use' index does not get overwritten with the new one after full index - MMBase

Details

Type: Bug
Status: Resolved
Priority: Critical
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 1.0
Component/s: None

Description:

This even results in not having *any* index since the initial index can never be build.

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

André van Toly added a comment - 2009-06-03 12:53

The copy has 7 items in the index, but the 'in use' index seems to have 0:

  in use: 0
  full index copy: 7

And after when I update a node from the index:

  in use: 1
  full index copy: 7

So, the index gets updated but not after a full index.

Show

André van Toly added a comment - 2009-06-03 12:53 The copy has 7 items in the index, but the 'in use' index seems to have 0: in use: 0 full index copy: 7 And after when I update a node from the index: in use: 1 full index copy: 7 So, the index gets updated but not after a full index.

People

Assignee:

Michiel Meeuwissen

Reporter:

André van Toly
Votes:

0

Watchers:

0

Dates

Due:

2009-05-27

Created:

2009-05-25 12:38

Updated:

2009-06-03 20:13

Resolved:

2009-06-03 20:13

LuceneModule

The 'in use' index does not get overwritten with the new one after full index

Details

Activity

People

Dates