[
https://issues.apache.org/jira/browse/DIRSERVER-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-824:
----------------------------------------
Fix Version/s: (was: 1.5.2)
2.0.0
Moved to 2.0.0, I see no easy way to fix this issue without modifying the
server architecture ...
> 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: 2.0.0
>
>
> As collective attributes never hit the database, they are not evaluated upon
> search operations if they are used in filters. This is an hard issue to fix
> but we may also support this kind of virtual attributes in the future, so we
> need a way to handle such cases. One solution can be injecting the collective
> attributes into entries before search operations. Other LDAP servers may be
> doing this. (I had felt this when I read their documents.) Hoever I am not
> sure about the negative effects of that way on performance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
