You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <ji...@apache.org> on 2007/08/23 17:40:30 UTC
[jira] Created: (DIRSERVER-1030) Add CascadeControl and add
functionality to cascade modify and delete effects
Add CascadeControl and add functionality to cascade modify and delete effects
-----------------------------------------------------------------------------
Key: DIRSERVER-1030
URL: https://issues.apache.org/jira/browse/DIRSERVER-1030
Project: Directory ApacheDS
Issue Type: New Feature
Affects Versions: 1.5.0
Reporter: Alex Karasulu
Fix For: 1.5.1
We need a marker request control to trigger cascaded deletes and modifications which factor into account dependencies when effecting these changes. The behavior of the control is context specific. This is need to do bulk operations on the schema which is heavily constrained due to interdependencies.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1030) Add CascadeControl and add
functionality to cascade modify and delete effects
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu updated DIRSERVER-1030:
-------------------------------------
Fix Version/s: (was: 1.5.3)
1.5.5
> Add CascadeControl and add functionality to cascade modify and delete effects
> -----------------------------------------------------------------------------
>
> Key: DIRSERVER-1030
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1030
> Project: Directory ApacheDS
> Issue Type: New Feature
> Affects Versions: 1.5.2, 1.5.1
> Reporter: Alex Karasulu
> Fix For: 1.5.5
>
>
> We need a marker request control to trigger cascaded deletes and modifications which factor into account dependencies when effecting these changes. The behavior of the control is context specific. This is need to do bulk operations on the schema which is heavily constrained due to interdependencies.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1030) Add CascadeControl and add
functionality to cascade modify and delete effects
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu updated DIRSERVER-1030:
-------------------------------------
Affects Version/s: (was: 1.5.0)
1.5.1
1.5.2
Fix Version/s: (was: 1.5.1)
1.5.3
The control was added for the protocol and made to tunnel down into the core of the server with various changes committed for this issue. However after some discussion the needs of the Directory studio product seemed not to require this modification however the control can still be implemented later on since it does server a purpose. However there is no urgency for it so we're moving it out to another release.
> Add CascadeControl and add functionality to cascade modify and delete effects
> -----------------------------------------------------------------------------
>
> Key: DIRSERVER-1030
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1030
> Project: Directory ApacheDS
> Issue Type: New Feature
> Affects Versions: 1.5.2, 1.5.1
> Reporter: Alex Karasulu
> Fix For: 1.5.3
>
>
> We need a marker request control to trigger cascaded deletes and modifications which factor into account dependencies when effecting these changes. The behavior of the control is context specific. This is need to do bulk operations on the schema which is heavily constrained due to interdependencies.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1030) Add CascadeControl and add
functionality to cascade modify and delete effects
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1030:
-----------------------------------------
Fix Version/s: (was: 1.5.5)
2.0.0-RC1
Postponed to 2.0.0-RC1
> Add CascadeControl and add functionality to cascade modify and delete effects
> -----------------------------------------------------------------------------
>
> Key: DIRSERVER-1030
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1030
> Project: Directory ApacheDS
> Issue Type: New Feature
> Affects Versions: 1.5.2, 1.5.1
> Reporter: Alex Karasulu
> Fix For: 2.0.0-RC1
>
>
> We need a marker request control to trigger cascaded deletes and modifications which factor into account dependencies when effecting these changes. The behavior of the control is context specific. This is need to do bulk operations on the schema which is heavily constrained due to interdependencies.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1030) Add CascadeControl and add
functionality to cascade modify and delete effects
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651215#action_12651215 ]
Emmanuel Lecharny commented on DIRSERVER-1030:
----------------------------------------------
Honnestly, I don't see how we can fix that for 1.5.5...
I think that even for 2.0, this is a bit too complex. 2.5 ?
> Add CascadeControl and add functionality to cascade modify and delete effects
> -----------------------------------------------------------------------------
>
> Key: DIRSERVER-1030
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1030
> Project: Directory ApacheDS
> Issue Type: New Feature
> Affects Versions: 1.5.2, 1.5.1
> Reporter: Alex Karasulu
> Fix For: 1.5.5
>
>
> We need a marker request control to trigger cascaded deletes and modifications which factor into account dependencies when effecting these changes. The behavior of the control is context specific. This is need to do bulk operations on the schema which is heavily constrained due to interdependencies.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.