[ https://issues.apache.org/jira/brow...ls:all-tabpanel ]

Alex Karasulu updated DIRSERVER-824:
------------------------------------

Fix Version/s:     (was: 1.5.0)
1.5.1

Emmanuel you're right this is a tough problem to solve efficiently.  I'll pu
t this one off until after 1.5.0.

Incidentally one way to implement this would be to give search some extra at
tributes to consider while attempting to match for the filter.  These additi
onal attributes can be merged into the entry used for evaluation.  This away
 any attribute can be injec
ted into an entry to effect evaluation regardless of the partition implement
ation.

Actually with this mechanism we can support several virtual/dynamic attribut
es.  What do you think about this idea?

> Collective attributes are not evaluated in search operations when they are
 used in filter expressions
> --------------------------------------------------------------------------
---------------------------
>
>                 Key: DIRSERVER-824
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-824
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.0.1, 1.5.0
>            Reporter: Ersin Er
>             Fix For: 1.5.1
>
>
> As collective attributes never hit the database, they are not evaluated upon searc
h operations if they are used in filters. This is an hard issue to fix but we may al
so support this kind of virtual attributes in the future, so we need a way to handle
 su
ch cases. One solution can be injecting the collective attributes into entri
es before search operations. Other LDAP servers may be doing this. (I had fe
lt this when I read their documents.) Hoever I am not sure about the negativ
e effects of that way on pe
rformance.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[ Post a follow-up to this message ]