Second the idea of putting it into CVS under HEAD instead of proposals. If this works as expected, it could be an alternative to the default indexer regardless of the nodestore. Since you have to specifically enable it, it does not break the existing code going towards Slide-2.1 final.
It sounds like Stefan's is more mature than my implementation, swalling some pride and recommend using his codebase. -D > -----Original Message----- > From: James Mason [mailto:[EMAIL PROTECTED] > Sent: Friday, October 15, 2004 10:12 AM > To: Slide Developers Mailing List > Subject: Re: LucenePropertiesIndexer > > > Stefan, > > I think it would be good to get the code into CVS as quick as possible > so you and Darren can work together a bit :). I would tend to > favor the > proposals section myself since it makes it clear which pieces belong > together, but I don't have an overwhelming burden there. Also, the > package name you suggested sounds fine to me. > > -James > > On Fri, 2004-10-15 at 06:56, Stefan L�tzkendorf wrote: > > Hi all, > > > > I have a first implmentation of a propertiesindexer base on lucene. > > > > Operators currenlty supported are: > > eq, lt, lte, gt, gte, is-collection, is-principal, and, or. > > Data types supported: > > String, Date, Int (Text will follow). > > > > It is transaction aware in a limited sense: the index is updeted > > only if a transaction is commited. > > > > It will be configurable for user defined properties (define > data type > > and anylyzer). > > > > I know that Darren is currently working on this stuff to so I'm > > thinking what to do. > > I would be glad to add this stuff as a new package in the > stores section > > "org.apache.slide.index.lucene". An other option would be > to add it to > > the proposals section (which is not my favorite (:-)). > > > > What do you think? > > Regards, Stefan > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
