[CPS-devel] Re: Lucene Path *Index* with depth

[Christian Klinger]

Anahide Tchertchian schrieb:
> Hi,
> 
> Julien Anguenot a écrit :
>> Hi,
>>
>> Christian Klinger wrote:
>>
>>> is it possible to enable a depth parameter in a path query?
>>>
>>> Example
>>>
>>> /Portal
>>> /Portal/AA
>>> /Portal/AA/BB
>>> /Portal/CC
>>>
>>>
>>> if i search with
>>>
>>> {'path':'/Portal','depth'=1}
>>>
>>> results are:  Portal, Portal/AA, PortalBB
>>>
>>> and if i search with:
>>>
>>>   {'path':'/Portal','depth'=2}
>>>
>>> results are: Portal, Portal/AA, Portal/AA/BB, Portal/AA/CC
>>
>>
>> nope this feature it's not implemented yet.
>>
>> Can you open a ticket within the Trac please ?
>> (See : http://www.cps-project.org/sections/development for instructions)
>>
>> Cheers,
> 
> Note that the CPSLuceneCatalog re-definition of the 
> IndexableObjectWrapper object holds a method named relative_path_depth 
> that does what you want, see:
> https://svn.nuxeo.org/trac/pub/browser/CPS3/products/CPSLuceneCatalog/trunk/wrapper.py 
> 

Ok this seems to be possible solution for me as well. Plone uses a 
ExtensibleObjectWrapper i think i can register your function and put the 
depth parameter in the catalog.

> 
> If you add an index with that name (relative_path_depth), it will be 
> indexed, provided you add the method on the IndexableObjectWrapper you 
> are using (if I'm not wrong, you're not using CPSLuceneCatalog, right?).

Yes you are right.. I try to adapt CPSLuceneCatalog to work with Plone.
All in all that works but there are some problems with portlets which 
were to slove now.


> 
> Regards,
> 

thx christian