directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSERVER-249) Filters with less specific attributes do not return matching entries with more specific attribute with the value
Date Tue, 08 Aug 2006 19:21:14 GMT
    [ http://issues.apache.org/jira/browse/DIRSERVER-249?page=comments#action_12426680 ] 
            
Alex Karasulu commented on DIRSERVER-249:
-----------------------------------------

To expand the filter expression tree so all descendent attributeTypes are considered in the
search we must have a fast way to lookup the descendents of an attributeType.  The best way
to do this is with a good old map of OID strings to a set of descendent attributeTypes.  When
we need access a simple lookup with iterator creation is suffient.

Now keeping this structure in synch with registrations is the key.  A recursive algorthm can
be used to walk the supierors of an attributeType and add that attributeType to the descendents
list of each supior until null or top superior is reached.  Note that we can exclude top in
this.


> Filters with less specific attributes do not return matching entries with more specific
attribute with the value
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-249
>                 URL: http://issues.apache.org/jira/browse/DIRSERVER-249
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.0-RC1
>            Reporter: Alex Karasulu
>         Assigned To: Alex Karasulu
>            Priority: Critical
>             Fix For: 1.0-RC4
>
>
> The filter, (name="Tori Amos") will not return an entry in scope that has a cn attribute
that equals "Tori Amos".  Or at least I think this is the case.  Workiing off memory here
so I would need to confirm this.
> One way in which this can be solved would be to expand and replace the node with all
the subclasses of the attribute.  For the example above we would expand out to (| (cn="Tori
Amos") (sn="Tori Amos") (name="Tori Amos") (givenName="Tori Amos) ).  This would work but
it would choke the search engine.  We could do this with an interceptor too ... i.e. transform
the filter on the way in to a search().
>  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message