BUG? Disappearing Lucene index entries
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-29-2006 10:30 AM
Hi
I create a number of nodes of custom type cms:contact in one place in a repo, under an instance of a subtype of sys:container.
I then create a number of nodes of custom type cms
rganisation (itself a subtype of sys:container) in another place in a repo. I create child associations between these nodes and some of the others, so I end up with something like:
cms:contacts
- cms:contact1
- cms:contact2
- cms:contact3
cms
rganisations
- cms
rganisation1
- cms:contact1
- cms
rganisation2
- cms:contact2
- cms
rganisation3
- cms:contact3
Both Lucene search and JCR API confirm this structure. the NodeService confirms that the primary association of the cms:contacts is to cms:contacts, and their other associations are secondary. All is well.
Using NodeService.deleteNode() I then delete cms
rganisations. The JCR api still says the contacts are there under cms:contacts, but Lucene says there is nothing there. If I get the node cms:contacts it still has 5 child associations according to the NodeService, and they are all primary.
So the entries appear to have been removed from the Lucene index.
What to do? Please help!
Dominic
I create a number of nodes of custom type cms:contact in one place in a repo, under an instance of a subtype of sys:container.
I then create a number of nodes of custom type cms

cms:contacts
- cms:contact1
- cms:contact2
- cms:contact3
cms

- cms

- cms:contact1
- cms

- cms:contact2
- cms

- cms:contact3
Both Lucene search and JCR API confirm this structure. the NodeService confirms that the primary association of the cms:contacts is to cms:contacts, and their other associations are secondary. All is well.
Using NodeService.deleteNode() I then delete cms

So the entries appear to have been removed from the Lucene index.
What to do? Please help!
Dominic
Labels:
- Labels:
-
Archive
6 REPLIES 6
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-29-2006 10:32 AM
sorry should have previewed that post. In the second structure, the contacts should be children of the cms
rganisation nodes:
cms
rganisations
.. cms
rganisation1
…. cms:contact1
.. cms
rganisation2
.. cms:contact2
…. cms
rganisation3
.. cms:contact3
Thanks
Dominic

cms

.. cms

…. cms:contact1
.. cms

.. cms:contact2
…. cms

.. cms:contact3
Thanks
Dominic
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-29-2006 10:44 AM
I should add that using xpath search the children also appear.
I'm confused!
I'm confused!

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-03-2006 04:32 AM
Hi
This sounds like a bug in delete in the lucene index code for secondary associations. I will look into this.
Regards
Andy
This sounds like a bug in delete in the lucene index code for secondary associations. I will look into this.
Regards
Andy

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-03-2006 12:29 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-03-2006 12:33 PM
Cheers Andy.
Thanks for swift reply. Thought it was something along those lines. Will have a play with your fix although I am having trouble with your svn repo…
svn: Berkeley DB error while opening 'transactions' table for filesystem /home/svnadmin/svn/alfresco-open-mirror/db:
Cannot allocate memory
No error
svn: bdb: Lock table is out of available locker entries
Thanks for swift reply. Thought it was something along those lines. Will have a play with your fix although I am having trouble with your svn repo…
svn: Berkeley DB error while opening 'transactions' table for filesystem /home/svnadmin/svn/alfresco-open-mirror/db:
Cannot allocate memory
No error
svn: bdb: Lock table is out of available locker entries

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-08-2007 06:30 AM
Hi
This has now been fixed. BTW, the suggested fix was not correct.
Regards
Andy
This has now been fixed. BTW, the suggested fix was not correct.
Regards
Andy
