Re: [Exist-open] Problem with only one file by collection in /db/system/comf

[Pierrick B. <pie...@cu...>]

Hi,

Patrick Turcotte a =E9crit :

> I'm working on a Generic Lucene Trigger.

An "indexing" trigger then :-) FYI : triggers have not been designed for=20
this (but that doesn't prevent you to write one). Also, we plan to=20
redesign the indexing API in a more modular way that could indeed feed=20
Lucene (or whatever) indexes.

> So I thought I'll place it in /db/system/conf/myCollection, beside the=20
> collection.xconf that define my trigger. But it seems there can only be=
=20
> one file by collection in there. Am I right?

Yes.

> Is there any reason?

Avoid multiple configuration files :-) I think this could lead to=20
confusion : what is an index is defined in one file and then in another=20
one ? Furthermore, accessing those files is a performance bottleneck.

> Seems to me a config folder would be an ideal place for the kind of fil=
e=20
> I'm needing here.

Ideally, you are probably right but see above.

> Also, in source (from svn/trunk) of=20
> org.exist.collections.Collection.checkConfiguration() there is a commen=
t=20
> by pb

I am pb ;-)

> saying that code should be modified to not throw exception if=20
> system property allows several ones.

Yes : my idea was roughly what you just describe :

> Maybe "collection.xconf" should be reserved to contain collection info=20
> (as index, triggers, etc.) and any file with differents names (maybe al=
l=20
> with .xconf or .conf.xml extension) allowed unless explicitly forbidden=
=20
> in $EXIST_HOME/conf.xml. This is what I expected at first.

... but I wonder if this design wouldn't have a huge impact on performanc=
e.

Well, you could at least start by rewriting collection configuration=20
handler in a more modular way that would be able to cope with key/value=20
pairs *as well as* more structured data. This would be handy for all of=20
us I think.

Cheers,

--=20
Pierrick Brihaye, informaticien
Service r=E9gional de l'Inventaire / DRAC Bretagne
mailto:pie...@cu... / t=E9l : +33 (0)2 99 29 67 78
Avez-vous lu http://usenet-fr.news.eu.org/fr-chartes/rfc1855.html ?