You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Ersin Er (JIRA)" <ji...@apache.org> on 2007/01/12 08:22:27 UTC
[jira] Created: (DIRSERVER-824) Collective attributes are not
evaluated in search operations when they are used in filter expressions
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
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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DIRSERVER-824) Collective attributes are not
evaluated in search operations when they are used in filter expressions
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ 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.1)
1.5.2
Again a massive issue to solve so let's push it off to 1.5.2.
> 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.2
>
>
> 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.
[jira] Updated: (DIRSERVER-824) Collective attributes are not
evaluated in search operations when they are used in filter expressions
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ 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: 2.0.0-RC1
(was: 2.0.0)
Moved back to 2.0.0-RC1
> 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.5.0, 1.0.1
> Reporter: Ersin Er
> Fix For: 2.0.0-RC1
>
>
> 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.
[jira] Updated: (DIRSERVER-824) Collective attributes are not
evaluated in search operations when they are used in filter expressions
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DIRSERVER-824) Collective attributes are not
evaluated in search operations when they are used in filter expressions
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529444 ]
Emmanuel Lecharny commented on DIRSERVER-824:
---------------------------------------------
We have had some more discussion about this issue yesturday.
We think that the solution would be to extract the LeafEvaluator out of the Partition, and to have a specific interceptor in charge of the filter evaluation.
This has two impacts :
1) we have to efficiently move the code from Partition to an interceptor, and to be sure that this interceptor is called after all the collectiveAttributes have been added to the entry)
2) we will have to modify the Partition interface to change the lookup method semantic
Not really easy ...
> 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.
[jira] Updated: (DIRSERVER-824) Collective attributes are not
evaluated in search operations when they are used in filter expressions
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DIRSERVER-824) Collective attributes are not
evaluated in search operations when they are used in filter expressions
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ 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: 1.5.0
I think this would be better to postpone this issue to 1.5.0 : we don't have real clues on how to fix it quickly in 1.0.1
> 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.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.
[jira] Commented: (DIRSERVER-824) Collective attributes are not
evaluated in search operations when they are used in filter expressions
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464304 ]
Emmanuel Lecharny commented on DIRSERVER-824:
---------------------------------------------
Injecting the collective attributes in the entry before storing the data will be shouting you in the feet : this is exactly what CA have been creating to : to avoid such duplication of data.
Now, having said that does not help at all to solve the pb ! (sorry :)
The good point is that filtering on CA helps a lot : you can discard a full branch if the c-l is not found in the subentry. But this can also becoming a hell, if the subtree selection is a complex one...
Now, what about doing something which is close to the idea you had :
- adding CA to the selected entries, before discarding or returning them ?
Suppose you select with a filter like (&(ObjectClass=person)(c-l=ankara)), and you get the entry :
dn: uid=ersiner,c=turkey,ou=people,dc=apache,dc=org
objectclass: top
objectclass: person
uid: ersiner
in the c=turkey,ou=people,dc=apache,dc=org associated subtree you have a c-l: ankara
now you clone the entry, add c-l= ankara, then apply the filters, then if it matches, return the entry
wdyt ?
> 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
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira