Re: New ExtendedPath index in Lucene?
Julien Anguenot <[email protected]>
| Newsgroups | gmane.comp.web.zope.cps.devel |
|---|---|
| Organization | Nuxeo SAS |
| Message-ID | <[email protected]> |
Lennart Regebro wrote: > On 2/12/07, Julien Anguenot <[email protected]> wrote: >> If you wanna implement this NXLucene side do the following : >> >> - implement a case in indexDocument() within server/core.py >> >> - Implement a case in searchDocuments() within the same server/core.py >> >> - A generic setup wrapper CPS side (CPSLuceneCatalog) and extend the >> possible options forward from Zope to NXLucene in nuxeo.lucene. > > No, that's not enough. I need to implement something that does > different matching on the fields, somehow. I know. and you need to do that in the server/core.py if you wanna do it at app level OR you can, perhaps, define a new Lucene index type (from Python through PyLucene it has to be checked because I'm not sure but I don't see why it shouldn't be) J. -- Julien Anguenot | Nuxeo R&D (Paris, France) Open Source ECM - http://www.nuxeo.com Nuxeo 5 : http://www.nuxeo.org Mobile: +33 (0) 6 72 57 57 66 _______________________________________________ cps-devel mailing list http://lists.nuxeo.com/mailman/listinfo/cps-devel
signature.asc
(application/pgp-signature, 252 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF0CyPGhoG8MxZ/pIRAg94AJ43jHtX+JK/UtnNrwbKdbVrupokUACdGOqH z/XCbrJJ9ljETNmK0WU7qY0= =+lAV -----END PGP SIGNATURE-----