Bug 42273 - Meta collection configuration
Summary: Meta collection configuration
Status: CLOSED FIXED
Alias: None
Product: Xindice
Classification: Unclassified
Component: DB Engine (show other bugs)
Version: cvs head (1.1)
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: Xindice Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-26 20:19 UTC by Natalia Shilenkova
Modified: 2007-04-27 17:53 UTC (History)
0 users



Attachments
meta.patch (4.40 KB, patch)
2007-04-26 20:23 UTC, Natalia Shilenkova
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Natalia Shilenkova 2007-04-26 20:19:18 UTC
Meta collection configuration is hard-coded and any changes to it are never
saved. What happens instead, when meta information is requested or updated,
database attempts to create new corresponding meta collection. If that
collection has been created in a previous run, its existing file will be used,
if not, new file will be created. 

This changes configuration at a runtime, so next request will find existing
collection, but after server is restarted all the configuration changes are
lost. It is not a big deal normally, but in some cases it causes incorrect
behavior. For example, meta collection will not be deleted with its
corresponding collection if there were no requests to it after server has been
restarted. If that collection is recreated, metadata for previously existed
collection with the same name will be used. 

This issue was described here:
http://marc.info/?l=xindice-users&m=117737647221091&w=2
Comment 1 Natalia Shilenkova 2007-04-26 20:23:32 UTC
Created attachment 20057 [details]
meta.patch

Patch has a suggestion on how issue could be fixed. This would allow metadata
collection to remember its configuration, similarly to database configuration.
Comment 2 Vadim Gritsenko 2007-04-27 17:53:22 UTC
applied, thanks.

it probably makes sense to move 'meta.xml' file management into the meta
collection itself. but it also makes sense to actually implement open()
separately from setConfig() in the Database and Collection - but all this should
wait till after release.