[
https://issues.apache.org/jira/browse/DIR-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny closed DIR-115.
---------------------------------
> Query string gets normilized in most cases (when normalization service is
> enabled)
> ----------------------------------------------------------------------------------
>
> Key: DIR-115
> URL: https://issues.apache.org/jira/browse/DIR-115
> Project: Directory
> Issue Type: Bug
> Environment: N/A
> Reporter: Giamma
> Assignee: Emmanuel Lecharny
>
> 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.
-
You can reply to this email to add a comment to the issue online.
