[jira] Commented: (DIR-115) Query string gets normilized in most cases (when normalization service is enabled)

["Emmanuel Lecharny (JIRA)" <di...@incubator.apache.org>]

    [ http://issues.apache.org/jira/browse/DIR-115?page=comments#action_12365174 ] 

Emmanuel Lecharny commented on DIR-115:
---------------------------------------

I 'm not sure that I understand the question, but here what I think :

cn is always normalized, accordingly to the SCHEMA  :
attributetype ( 2.5.4.41 NAME 'name'
    ...
    EQUALITY caseIgnoreMatch
    SUBSTR caseIgnoreSubstringsMatch
    ...)

attributetype ( 2.5.4.3 NAME ( 'cn' 'commonName' )
    ...
    SUP name )

To declare a new attribute that is case insensitive, one should use the same syntax :
attributetype ( <oid> NAME '<name>'
    ...
    EQUALITY caseIgnoreMatch
    SUBSTR caseIgnoreSubstringsMatch
    ...)

and compile the schema with this new attribute.

So, what is the status of this issue? May we close it or is there any other problem?


> Query string gets normilized in most cases (when normalization service is enabled)
> ----------------------------------------------------------------------------------
>
>          Key: DIR-115
>          URL: http://issues.apache.org/jira/browse/DIR-115
>      Project: Directory
>         Type: Bug
>  Environment: N/A
>     Reporter: Giamma
>     Assignee: Alex Karasulu

>
> I am submitting a query like this:
> "cn=Joe Black"
> When I process the query string from my custom partition, I get:
> "cn=joe black"
> How can I implement EQUALITY caseIgnoreMatch  or EQUALITY caseExactMatch, if the original casing is gone ?
> But when I run a query with a custom attribute, defined in the schema, the query string is not normailized.
> All the logic seems to be in this class ValueNormalizingVisitor.visit():
> normalized = ncn.normalizeByName( snode.getAttribute(), snode.getValue() ); 
> ncn.normalizeByName will normalize for standard atttributes, but not for custom attributes added to the schema.
> At the very least the code is not consistent. but I argue that it should not normilize the query string.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira