[jira] [Updated] (DIRSERVER-2153) We don't have to update the RDN index up to the top when moving an entry

2024-02-13 Thread Pierre Smits (Jira)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated DIRSERVER-2153:

Fix Version/s: Upcoming release
   (was: 2.0.0.AM27)

> We don't have to update the RDN index up to the top when moving an entry
> 
>
> Key: DIRSERVER-2153
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2153
> Project: Directory ApacheDS
>  Issue Type: Improvement
>  Components: backend, ldap
>Affects Versions: 2.0.0-M21
>Reporter: Emmanuel Lécharny
>Priority: Major
> Fix For: Upcoming release
>
>
> When we move an entry, we update all the ascendants up to the root, in order 
> to update the number of descendants. 
> We can save us a few updates by stopping when we met the common ascendant, 
> because it will have the same descendant number.
> For instance, moving an entry from A/B/C/D/xxx to A/B/E/F/xxx will decrement 
> the {{nbSubordinate}} counter for C and D, increment it for E and F, but for 
> B, it will remain the same.
> Doing so, in this very example, we would save 4 updates, dividing by 2 the 
> number of updates.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2153) We don't have to update the RDN index up to the top when moving an entry

2020-03-19 Thread Jira


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Emmanuel Lécharny updated DIRSERVER-2153:
-
Fix Version/s: (was: 2.0.0.AM26)
   2.0.0.AM27

> We don't have to update the RDN index up to the top when moving an entry
> 
>
> Key: DIRSERVER-2153
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2153
> Project: Directory ApacheDS
>  Issue Type: Improvement
>  Components: backend, ldap
>Affects Versions: 2.0.0-M21
>Reporter: Emmanuel Lécharny
>Priority: Major
> Fix For: 2.0.0.AM27
>
>
> When we move an entry, we update all the ascendants up to the root, in order 
> to update the number of descendants. 
> We can save us a few updates by stopping when we met the common ascendant, 
> because it will have the same descendant number.
> For instance, moving an entry from A/B/C/D/xxx to A/B/E/F/xxx will decrement 
> the {{nbSubordinate}} counter for C and D, increment it for E and F, but for 
> B, it will remain the same.
> Doing so, in this very example, we would save 4 updates, dividing by 2 the 
> number of updates.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2153) We don't have to update the RDN index up to the top when moving an entry

2019-06-16 Thread Emmanuel Lecharny (JIRA)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Emmanuel Lecharny updated DIRSERVER-2153:
-
Component/s: ldap
 backend

> We don't have to update the RDN index up to the top when moving an entry
> 
>
> Key: DIRSERVER-2153
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2153
> Project: Directory ApacheDS
>  Issue Type: Improvement
>  Components: backend, ldap
>Affects Versions: 2.0.0-M21
>Reporter: Emmanuel Lecharny
>Priority: Major
> Fix For: 2.0.0.AM26
>
>
> When we move an entry, we update all the ascendants up to the root, in order 
> to update the number of descendants. 
> We can save us a few updates by stopping when we met the common ascendant, 
> because it will have the same descendant number.
> For instance, moving an entry from A/B/C/D/xxx to A/B/E/F/xxx will decrement 
> the {{nbSubordinate}} counter for C and D, increment it for E and F, but for 
> B, it will remain the same.
> Doing so, in this very example, we would save 4 updates, dividing by 2 the 
> number of updates.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org



[jira] [Updated] (DIRSERVER-2153) We don't have to update the RDN index up to the top when moving an entry

2018-08-17 Thread Emmanuel Lecharny (JIRA)


 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Emmanuel Lecharny updated DIRSERVER-2153:
-
Fix Version/s: (was: 2.0.0.AM25)
   2.0.0.AM26

> We don't have to update the RDN index up to the top when moving an entry
> 
>
> Key: DIRSERVER-2153
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2153
> Project: Directory ApacheDS
>  Issue Type: Improvement
>Affects Versions: 2.0.0-M21
>Reporter: Emmanuel Lecharny
>Priority: Major
> Fix For: 2.0.0.AM26
>
>
> When we move an entry, we update all the ascendants up to the root, in order 
> to update the number of descendants. 
> We can save us a few updates by stopping when we met the common ascendant, 
> because it will have the same descendant number.
> For instance, moving an entry from A/B/C/D/xxx to A/B/E/F/xxx will decrement 
> the {{nbSubordinate}} counter for C and D, increment it for E and F, but for 
> B, it will remain the same.
> Doing so, in this very example, we would save 4 updates, dividing by 2 the 
> number of updates.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DIRSERVER-2153) We don't have to update the RDN index up to the top when moving an entry

2018-01-22 Thread Emmanuel Lecharny (JIRA)

 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Emmanuel Lecharny updated DIRSERVER-2153:
-
Fix Version/s: (was: 2.0.0-M24)
   2.0.0-M25

> We don't have to update the RDN index up to the top when moving an entry
> 
>
> Key: DIRSERVER-2153
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2153
> Project: Directory ApacheDS
>  Issue Type: Improvement
>Affects Versions: 2.0.0-M21
>Reporter: Emmanuel Lecharny
>Priority: Major
> Fix For: 2.0.0-M25
>
>
> When we move an entry, we update all the ascendants up to the root, in order 
> to update the number of descendants. 
> We can save us a few updates by stopping when we met the common ascendant, 
> because it will have the same descendant number.
> For instance, moving an entry from A/B/C/D/xxx to A/B/E/F/xxx will decrement 
> the {{nbSubordinate}} counter for C and D, increment it for E and F, but for 
> B, it will remain the same.
> Doing so, in this very example, we would save 4 updates, dividing by 2 the 
> number of updates.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DIRSERVER-2153) We don't have to update the RDN index up to the top when moving an entry

2016-11-20 Thread Stefan Seelmann (JIRA)

 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seelmann updated DIRSERVER-2153:
---
Fix Version/s: (was: 2.0.0-M23)
   2.0.0-M24

> We don't have to update the RDN index up to the top when moving an entry
> 
>
> Key: DIRSERVER-2153
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2153
> Project: Directory ApacheDS
>  Issue Type: Improvement
>Affects Versions: 2.0.0-M21
>Reporter: Emmanuel Lecharny
> Fix For: 2.0.0-M24
>
>
> When we move an entry, we update all the ascendants up to the root, in order 
> to update the number of descendants. 
> We can save us a few updates by stopping when we met the common ascendant, 
> because it will have the same descendant number.
> For instance, moving an entry from A/B/C/D/xxx to A/B/E/F/xxx will decrement 
> the {{nbSubordinate}} counter for C and D, increment it for E and F, but for 
> B, it will remain the same.
> Doing so, in this very example, we would save 4 updates, dividing by 2 the 
> number of updates.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (DIRSERVER-2153) We don't have to update the RDN index up to the top when moving an entry

2016-07-17 Thread Emmanuel Lecharny (JIRA)

 [ 
https://issues.apache.org/jira/browse/DIRSERVER-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Emmanuel Lecharny updated DIRSERVER-2153:
-
Fix Version/s: (was: 2.0.0-M22)
   2.0.0-M23

> We don't have to update the RDN index up to the top when moving an entry
> 
>
> Key: DIRSERVER-2153
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2153
> Project: Directory ApacheDS
>  Issue Type: Improvement
>Affects Versions: 2.0.0-M21
>Reporter: Emmanuel Lecharny
> Fix For: 2.0.0-M23
>
>
> When we move an entry, we update all the ascendants up to the root, in order 
> to update the number of descendants. 
> We can save us a few updates by stopping when we met the common ascendant, 
> because it will have the same descendant number.
> For instance, moving an entry from A/B/C/D/xxx to A/B/E/F/xxx will decrement 
> the {{nbSubordinate}} counter for C and D, increment it for E and F, but for 
> B, it will remain the same.
> Doing so, in this very example, we would save 4 updates, dividing by 2 the 
> number of updates.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)