[
https://issues.apache.org/jira/browse/DIRAPI-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16829731#comment-16829731
]
Emmanuel Lecharny commented on DIRAPI-104:
------------------------------------------
Postponing to a future 3.0 version.
Modifying an existing schema i snot easy, as it may break a server database,
especially when we add or remove a {{MUST}} member (or remove a {{MAY}}
member), as it may impact existing entries.
> Schema registries are not getting updated after adding a new AT to an
> ObjectClass entry present in the Schema partition
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: DIRAPI-104
> URL: https://issues.apache.org/jira/browse/DIRAPI-104
> Project: Directory Client API
> Issue Type: Bug
> Reporter: Kiran Ayyagari
> Priority: Critical
> Fix For: 3.0.0
>
>
> When a new mandatory(MUST) AT is added to an existing OC then this new OC is
> not properly loaded into the schema registries, as a result server is not
> able to prevent invalid entries from getting added.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
