Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <48A1403F.5050900@netcetera.ch>
Date: Tue, 12 Aug 2008 09:48:15 +0200
From: Wolfgang Habicht <wolfgang.habicht@netcetera.ch>
Reply-To: wolfgang.habicht@netcetera.ch
Organization: Netcetera AG
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: users@jackrabbit.apache.org
Subject: inconstistent index - query result does not match nodes accessed
 through their path
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi

we have diagnosed a strange behavior on using Jackrabbit 1.3.3:
After adding/modifying a node we get different results whether accessing 
the node directly through its path (correct answer) or by using the 
query engine (node does not exist/old value).
It seems that the search-index is not always correctly updated.

Does anyone know this problem?
What do you think, should it help to upgrade to Lucene 2.2.0 or 2.3.2? 
Is upgrading Lucene possible without any code change?

Additional information:
For the query we use SearchManager.createQuery(...).execute();
A simple restart of the system does not help, however deleting the index 
before starting again helps.


Thanks,
Wolfgang Habicht