-----Original Message----- From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED] Sent: Fri 1/16/2004 11:02 AM To: Slide Developers Mailing List Cc: Subject: Re: Proposal : index store - Lucene >hey, that's unfair. Christophe is doing a 'proposal' and the best way >to put something going is to get the code done and let people patch >it.... but without a code to start people won't start. so I think a <seed is great, any seed. ??? don't understand - maybe because my english is not very good ! I need this feature, I started it and I just want to have some feedbacks from the Slide commiters. I will be very happy to receive a lot of feedbacks in order to continue the implementation. I did that because all Slide commiters seems to be very busy. >I would not index the metadata with lucene, otherwise, it would >generate a mess and semantic collision between metadata and search. for >example, say you want to do a full-text search of 'author' and you have >your own properties that have author in it... all documents come >upjavascript:SetCmd(cmdSend); Send in >the search, but that's not what you wanted. Agree in this case but with Lucene, you can define properties as keyword or text field depending of your needs. If you store your properties in one store (eg. DB) and used index store engine for content search, I expected to have some performance issues when you search on prop and content. Anyway, Do you have some idea to optimize the current search service ? Why not to support both situation : either inder the prop or not ? Christophe
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
