[
https://issues.apache.org/jira/browse/DIRSERVER-824?page=com.atlassian.jira.plugin.system.issuetabpanels: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 put
this one off until after 1.5.0.
Incidentally one way to implement this would be to give search some extra
attributes to consider while attempting to match for the filter. These
additional attributes can be merged into the entry used for evaluation. This
away any attribute can be injected into an entry to effect evaluation
regardless of the partition implementation.
Actually with this mechanism we can support several virtual/dynamic attributes.
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
> 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.
