topic Re: Lucene search returns out of sync data within transaction in Alfresco Archive

Lucene search returns out of sync data within transaction

timster — Thu, 06 Apr 2006 19:28:32 GMT

We're getting into the nuts and bolts of Alfresco for some work we're doing, and i'm running into a data sync issue with one of the unit tests I've written.We are using Spring's transactional setup, which Alfresco is picking up very nicely, and you all may be aware that Spring has transaction-enable

Re: Lucene search returns out of sync data within transaction

andy — Fri, 07 Apr 2006 09:29:00 GMT

Hi

This behaviour is not expected.

It seems a delete against data added/changed in the transaction may not be picked up if it is the last action on the transaction. (In the unit test there is an add after the delete - I have split this out and reproduced the issue). If a pre-existing node is deleted the behaviour is OK, if you add or update a node the count will be correct.

See http://www.alfresco.org/jira/browse/AR-549
The fix will go in soon and is added as a comment to the bug.

Regards

Andy

Re: Lucene search returns out of sync data within transaction

andy — Fri, 07 Apr 2006 09:41:38 GMT

Hi

This is fixed in the HEAD code stream.

The committed index will be correct.

The only way you can work round this is to update any node after the delete, get the fixed code, or apply the same fix.

Regards

Andy