There is a decades long discussion on what is data and what is metadata and I don't want to touch that with a stick, but I think that if you need to do full-text search on your metadata there is something wrong.
Sometime mailing list gives a lot of confusion :-) I'm sorry I think my explaination was not good ! I don't want to make full text search on my metata.
It is a simple use case : give me all documents where author = "John Smith" and where the document content contains "Cms repository open source". As you explained correctly, author is a metadat defined in a DB and for me the document content is tokenized into an index (like Lucene). So, I you have one store for the metata (DB) and another store for full text search (eg.Lucene), you need to make the intersection between the query on the DB and the query made across Lucene. With Lucene, you can also store your metadata called 'Keyword' and It will be certainly fast.
As usual :-)
I think we need to attack the store/indexing problem from the scenario angle down... or we'll go around in circles for a long time. of course, I'm not talking about Slide 2.0 but something to do after the release is done.
Christophe
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
