Re: New ExtendedPath index in Lucene?
"Lennart Regebro" <[email protected]>
| Newsgroups | gmane.comp.web.zope.cps.devel |
|---|---|
| Message-ID | <[email protected]> |
On 2/12/07, Julien Anguenot <[email protected]> wrote: > I know. and you need to do that in the server/core.py if you wanna do it > at app level But there is no matching done there. All that does is add terms to a query. The actual matching is done in the Java somewhere, I don't know exactly where yet (although I'm trying to figure it out). > OR you can, perhaps, define a new Lucene index type Maybe, but I don't know how that is done. The closest I've come is to define a new Term, but I haven't been able to override the matching method (I've tried compareTo, equals and __cmp__). So I thought maybe I need a new field. But the fields are created with PyLucene.Field.Keyword() and similar, and I can't find that method in the source, so I don't actually know what it does and what to override... -- Lennart Regebro: Python, Zope, CPS, Plone consulting. +33 661 58 14 64 _______________________________________________ cps-devel mailing list http://lists.nuxeo.com/mailman/listinfo/cps-devel