You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Kevin Kovach (JIRA)" <ji...@apache.org> on 2009/03/09 17:04:50 UTC
[jira] Created: (DIRSERVER-1326) Unable to search on a custom
attribute of type directory string unless I've set a matching rule
Unable to search on a custom attribute of type directory string unless I've set a matching rule
-----------------------------------------------------------------------------------------------
Key: DIRSERVER-1326
URL: https://issues.apache.org/jira/browse/DIRSERVER-1326
Project: Directory ApacheDS
Issue Type: Bug
Affects Versions: 1.5.4
Environment: 64-bit Ubuntu Linux, Java version 1.6.0_12
Reporter: Kevin Kovach
I have created a custom auxiliary objectclass with one custom attribute. That attribute is of type directory string, and is used as an id. Here are the schema objects. I have replaced my OID with x.x.x.x
dn: m-oid=x.x.x.x.1.16, ou=objectClasses, cn=myschema, ou=schema
objectclass: metaObjectClass
objectclass: metaTop
objectclass: top
m-oid: x.x.x.x.1.16
m-name: myObject
m-typeObjectClass: AUXILIARY
m-must: myId
dn: m-oid=x.x.x.x.1.15, ou=attributeTypes, cn=myschema, ou=schema
objectclass: metaAttributeType
objectclass: metaTop
objectclass: top
m-oid: x.x.x.x.1.15
m-name: myId
m-syntax: 1.3.6.1.4.1.1466.115.121.1.15
m-singleValue: TRUE
I have populated my directory with several objects of this custom objectclass type, which contain the custom id attribute. When I attempt to search the DIT for an object with a specific value for myId, I get the following error...
ERROR httpSSLWorkerThread-8081-0 localhost - NamingException: [LDAP: error code 80 - OTHER: failed for SearchRequest
baseDn : '2.5.4.11=myorg,0.9.2342.19200300.100.1.25=mydomain,0.9.2342.19200300.100.1.25=com'
filter : '(x.x.x.x.1.15=j9cinXz40mEpCI6cWxZJ70ETV:[9223372036854775807])'
scope : whole subtree
typesOnly : false
Size Limit : no limit
Time Limit : no limit
Deref Aliases : deref Always
attributes :
: java.lang.String cannot be cast to [B]
If I modify the custom attribute to have a matching rule of "m-equality: caseExactMatch" then the error seems to go away.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DIRSERVER-1326) Unable to search on a custom
attribute of type directory string unless I've set a matching rule
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny reassigned DIRSERVER-1326:
--------------------------------------------
Assignee: Emmanuel Lecharny
> Unable to search on a custom attribute of type directory string unless I've set a matching rule
> -----------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1326
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1326
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.4
> Environment: 64-bit Ubuntu Linux, Java version 1.6.0_12
> Reporter: Kevin Kovach
> Assignee: Emmanuel Lecharny
>
> I have created a custom auxiliary objectclass with one custom attribute. That attribute is of type directory string, and is used as an id. Here are the schema objects. I have replaced my OID with x.x.x.x
> dn: m-oid=x.x.x.x.1.16, ou=objectClasses, cn=myschema, ou=schema
> objectclass: metaObjectClass
> objectclass: metaTop
> objectclass: top
> m-oid: x.x.x.x.1.16
> m-name: myObject
> m-typeObjectClass: AUXILIARY
> m-must: myId
> dn: m-oid=x.x.x.x.1.15, ou=attributeTypes, cn=myschema, ou=schema
> objectclass: metaAttributeType
> objectclass: metaTop
> objectclass: top
> m-oid: x.x.x.x.1.15
> m-name: myId
> m-syntax: 1.3.6.1.4.1.1466.115.121.1.15
> m-singleValue: TRUE
> I have populated my directory with several objects of this custom objectclass type, which contain the custom id attribute. When I attempt to search the DIT for an object with a specific value for myId, I get the following error...
> ERROR httpSSLWorkerThread-8081-0 localhost - NamingException: [LDAP: error code 80 - OTHER: failed for SearchRequest
> baseDn : '2.5.4.11=myorg,0.9.2342.19200300.100.1.25=mydomain,0.9.2342.19200300.100.1.25=com'
> filter : '(x.x.x.x.1.15=j9cinXz40mEpCI6cWxZJ70ETV:[9223372036854775807])'
> scope : whole subtree
> typesOnly : false
> Size Limit : no limit
> Time Limit : no limit
> Deref Aliases : deref Always
> attributes :
> : java.lang.String cannot be cast to [B]
> If I modify the custom attribute to have a matching rule of "m-equality: caseExactMatch" then the error seems to go away.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DIRSERVER-1326) Unable to search on a custom
attribute of type directory string unless I've set a matching rule
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny resolved DIRSERVER-1326.
------------------------------------------
Resolution: Fixed
This was a nasty bug in the EqualityEvaluator class, which assumed that when we didn't have a Comparator for an AttributeType, then the associated values were necessary binary, which is obviously wrong if you define the AttributeType with a HumanReadable syntax (like DirectoryString).
Fixed in http://svn.apache.org/viewvc?rev=751812&view=rev
> Unable to search on a custom attribute of type directory string unless I've set a matching rule
> -----------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1326
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1326
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.4
> Environment: 64-bit Ubuntu Linux, Java version 1.6.0_12
> Reporter: Kevin Kovach
> Assignee: Emmanuel Lecharny
>
> I have created a custom auxiliary objectclass with one custom attribute. That attribute is of type directory string, and is used as an id. Here are the schema objects. I have replaced my OID with x.x.x.x
> dn: m-oid=x.x.x.x.1.16, ou=objectClasses, cn=myschema, ou=schema
> objectclass: metaObjectClass
> objectclass: metaTop
> objectclass: top
> m-oid: x.x.x.x.1.16
> m-name: myObject
> m-typeObjectClass: AUXILIARY
> m-must: myId
> dn: m-oid=x.x.x.x.1.15, ou=attributeTypes, cn=myschema, ou=schema
> objectclass: metaAttributeType
> objectclass: metaTop
> objectclass: top
> m-oid: x.x.x.x.1.15
> m-name: myId
> m-syntax: 1.3.6.1.4.1.1466.115.121.1.15
> m-singleValue: TRUE
> I have populated my directory with several objects of this custom objectclass type, which contain the custom id attribute. When I attempt to search the DIT for an object with a specific value for myId, I get the following error...
> ERROR httpSSLWorkerThread-8081-0 localhost - NamingException: [LDAP: error code 80 - OTHER: failed for SearchRequest
> baseDn : '2.5.4.11=myorg,0.9.2342.19200300.100.1.25=mydomain,0.9.2342.19200300.100.1.25=com'
> filter : '(x.x.x.x.1.15=j9cinXz40mEpCI6cWxZJ70ETV:[9223372036854775807])'
> scope : whole subtree
> typesOnly : false
> Size Limit : no limit
> Time Limit : no limit
> Deref Aliases : deref Always
> attributes :
> : java.lang.String cannot be cast to [B]
> If I modify the custom attribute to have a matching rule of "m-equality: caseExactMatch" then the error seems to go away.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1326) Unable to search on a custom
attribute of type directory string unless I've set a matching rule
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1326:
-----------------------------------------
Fix Version/s: 1.5.5
> Unable to search on a custom attribute of type directory string unless I've set a matching rule
> -----------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1326
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1326
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.4
> Environment: 64-bit Ubuntu Linux, Java version 1.6.0_12
> Reporter: Kevin Kovach
> Assignee: Emmanuel Lecharny
> Fix For: 1.5.5
>
>
> I have created a custom auxiliary objectclass with one custom attribute. That attribute is of type directory string, and is used as an id. Here are the schema objects. I have replaced my OID with x.x.x.x
> dn: m-oid=x.x.x.x.1.16, ou=objectClasses, cn=myschema, ou=schema
> objectclass: metaObjectClass
> objectclass: metaTop
> objectclass: top
> m-oid: x.x.x.x.1.16
> m-name: myObject
> m-typeObjectClass: AUXILIARY
> m-must: myId
> dn: m-oid=x.x.x.x.1.15, ou=attributeTypes, cn=myschema, ou=schema
> objectclass: metaAttributeType
> objectclass: metaTop
> objectclass: top
> m-oid: x.x.x.x.1.15
> m-name: myId
> m-syntax: 1.3.6.1.4.1.1466.115.121.1.15
> m-singleValue: TRUE
> I have populated my directory with several objects of this custom objectclass type, which contain the custom id attribute. When I attempt to search the DIT for an object with a specific value for myId, I get the following error...
> ERROR httpSSLWorkerThread-8081-0 localhost - NamingException: [LDAP: error code 80 - OTHER: failed for SearchRequest
> baseDn : '2.5.4.11=myorg,0.9.2342.19200300.100.1.25=mydomain,0.9.2342.19200300.100.1.25=com'
> filter : '(x.x.x.x.1.15=j9cinXz40mEpCI6cWxZJ70ETV:[9223372036854775807])'
> scope : whole subtree
> typesOnly : false
> Size Limit : no limit
> Time Limit : no limit
> Deref Aliases : deref Always
> attributes :
> : java.lang.String cannot be cast to [B]
> If I modify the custom attribute to have a matching rule of "m-equality: caseExactMatch" then the error seems to go away.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.