You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2009/08/12 00:34:14 UTC
[jira] Created: (DIRSERVER-1399) The modify() operation does not
use MR to compare values
The modify() operation does not use MR to compare values
--------------------------------------------------------
Key: DIRSERVER-1399
URL: https://issues.apache.org/jira/browse/DIRSERVER-1399
Project: Directory ApacheDS
Issue Type: Bug
Affects Versions: 1.5.4
Reporter: Emmanuel Lecharny
Priority: Critical
Fix For: 1.5.5
When modifying values, either adding or removing them, we don't use the Comparator associated with the AT matchingRule to compare values. This lead to big problem when the values are not equals even after a normalization (for instance, the syntaxCheckers attribute's value might differ), as the value is not found.
We have to :
- use the comparators instead of the simple comparison
- add the missing comparators for the schema elements
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1399) The modify() operation does not
use MR to compare values
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742326#action_12742326 ]
Emmanuel Lecharny commented on DIRSERVER-1399:
----------------------------------------------
Added the Comparator, Normalizer and SyntaxChecker comparators.
Modified the modify() method to use the compareTo() instead of a straight String comparison
> The modify() operation does not use MR to compare values
> --------------------------------------------------------
>
> Key: DIRSERVER-1399
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1399
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.4
> Reporter: Emmanuel Lecharny
> Assignee: Emmanuel Lecharny
> Priority: Critical
> Fix For: 1.5.5
>
>
> When modifying values, either adding or removing them, we don't use the Comparator associated with the AT matchingRule to compare values. This lead to big problem when the values are not equals even after a normalization (for instance, the syntaxCheckers attribute's value might differ), as the value is not found.
> We have to :
> - use the comparators instead of the simple comparison
> - add the missing comparators for the schema elements
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DIRSERVER-1399) The modify() operation does not use
MR to compare values
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny closed DIRSERVER-1399.
----------------------------------------
> The modify() operation does not use MR to compare values
> --------------------------------------------------------
>
> Key: DIRSERVER-1399
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1399
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.4
> Reporter: Emmanuel Lecharny
> Assignee: Emmanuel Lecharny
> Priority: Critical
> Fix For: 2.0.0-RC1
>
>
> When modifying values, either adding or removing them, we don't use the Comparator associated with the AT matchingRule to compare values. This lead to big problem when the values are not equals even after a normalization (for instance, the syntaxCheckers attribute's value might differ), as the value is not found.
> We have to :
> - use the comparators instead of the simple comparison
> - add the missing comparators for the schema elements
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DIRSERVER-1399) The modify() operation does not
use MR to compare values
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny resolved DIRSERVER-1399.
------------------------------------------
Resolution: Duplicate
This is now a duplicate of DIRSERVER-1402, which is currently being processed. Many comparators have been added, a few are still missing.
> The modify() operation does not use MR to compare values
> --------------------------------------------------------
>
> Key: DIRSERVER-1399
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1399
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.4
> Reporter: Emmanuel Lecharny
> Assignee: Emmanuel Lecharny
> Priority: Critical
> Fix For: 2.0.0-RC1
>
>
> When modifying values, either adding or removing them, we don't use the Comparator associated with the AT matchingRule to compare values. This lead to big problem when the values are not equals even after a normalization (for instance, the syntaxCheckers attribute's value might differ), as the value is not found.
> We have to :
> - use the comparators instead of the simple comparison
> - add the missing comparators for the schema elements
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DIRSERVER-1399) The modify() operation does not
use MR to compare values
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny reassigned DIRSERVER-1399:
--------------------------------------------
Assignee: Emmanuel Lecharny
> The modify() operation does not use MR to compare values
> --------------------------------------------------------
>
> Key: DIRSERVER-1399
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1399
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.4
> Reporter: Emmanuel Lecharny
> Assignee: Emmanuel Lecharny
> Priority: Critical
> Fix For: 1.5.5
>
>
> When modifying values, either adding or removing them, we don't use the Comparator associated with the AT matchingRule to compare values. This lead to big problem when the values are not equals even after a normalization (for instance, the syntaxCheckers attribute's value might differ), as the value is not found.
> We have to :
> - use the comparators instead of the simple comparison
> - add the missing comparators for the schema elements
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1399) The modify() operation does not
use MR to compare values
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1399:
-----------------------------------------
Fix Version/s: (was: 1.5.5)
2.0.0-RC1
Postponed
> The modify() operation does not use MR to compare values
> --------------------------------------------------------
>
> Key: DIRSERVER-1399
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1399
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.4
> Reporter: Emmanuel Lecharny
> Assignee: Emmanuel Lecharny
> Priority: Critical
> Fix For: 2.0.0-RC1
>
>
> When modifying values, either adding or removing them, we don't use the Comparator associated with the AT matchingRule to compare values. This lead to big problem when the values are not equals even after a normalization (for instance, the syntaxCheckers attribute's value might differ), as the value is not found.
> We have to :
> - use the comparators instead of the simple comparison
> - add the missing comparators for the schema elements
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.