[jira] Created: (DIRSERVER-776) entryUUID only created when entries are added with Mitosis enabled

entryUUID only created when entries are added with Mitosis enabled
------------------------------------------------------------------

                 Key: DIRSERVER-776
                 URL: http://issues.apache.org/jira/browse/DIRSERVER-776
             Project: Directory ApacheDS
          Issue Type: Bug
          Components: core, mitosis
            Reporter: Alex Karasulu
             Fix For: 1.5.0


It would be nice to refactor out the UUID injection into standard interceptors so that entries have UUID attributes even if mitosis is not enabled.  This way when Mitosis is turned on the database need not be rebuilt from scratch.  

Another work around would be to add a UUID generation tool to add this attribute if replication is to be used but this is a poor work around for the problem.  Question is do you want to deal with the overhead of this UUID attribute for each entry without needing mitosis?  In general it's probably a good idea to have this in effect all the time.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ http://issues.apache.org/jira/browse/DIRSERVER-776?page=all ]

Alex Karasulu closed DIRSERVER-776.
-----------------------------------

    Resolution: Fixed

Fixed here http://svn.apache.org/viewvc?view=rev&revision=471971

> entryUUID only created when entries are added with Mitosis enabled
> ------------------------------------------------------------------
>
>                 Key: DIRSERVER-776
>                 URL: http://issues.apache.org/jira/browse/DIRSERVER-776
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core, mitosis
>            Reporter: Alex Karasulu
>             Fix For: 1.5.0
>
>
> It would be nice to refactor out the UUID injection into standard interceptors so that entries have UUID attributes even if mitosis is not enabled.  This way when Mitosis is turned on the database need not be rebuilt from scratch.  
> Another work around would be to add a UUID generation tool to add this attribute if replication is to be used but this is a poor work around for the problem.  Question is do you want to deal with the overhead of this UUID attribute for each entry without needing mitosis?  In general it's probably a good idea to have this in effect all the time.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ http://issues.apache.org/jira/browse/DIRSERVER-776?page=all ]

Alex Karasulu reopened DIRSERVER-776:
-------------------------------------

             
Ok this stinks.  If the entry marked deleted has descendents this code will fail.  We need to recursively delete the entire dead branch depth first.

> entryUUID only created when entries are added with Mitosis enabled
> ------------------------------------------------------------------
>
>                 Key: DIRSERVER-776
>                 URL: http://issues.apache.org/jira/browse/DIRSERVER-776
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core, mitosis
>            Reporter: Alex Karasulu
>             Fix For: 1.5.0
>
>
> It would be nice to refactor out the UUID injection into standard interceptors so that entries have UUID attributes even if mitosis is not enabled.  This way when Mitosis is turned on the database need not be rebuilt from scratch.  
> Another work around would be to add a UUID generation tool to add this attribute if replication is to be used but this is a poor work around for the problem.  Question is do you want to deal with the overhead of this UUID attribute for each entry without needing mitosis?  In general it's probably a good idea to have this in effect all the time.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ http://issues.apache.org/jira/browse/DIRSERVER-776?page=all ]

Alex Karasulu reassigned DIRSERVER-776:
---------------------------------------

    Assignee: Alex Karasulu

> entryUUID only created when entries are added with Mitosis enabled
> ------------------------------------------------------------------
>
>                 Key: DIRSERVER-776
>                 URL: http://issues.apache.org/jira/browse/DIRSERVER-776
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core, mitosis
>            Reporter: Alex Karasulu
>         Assigned To: Alex Karasulu
>             Fix For: 1.5.0
>
>
> It would be nice to refactor out the UUID injection into standard interceptors so that entries have UUID attributes even if mitosis is not enabled.  This way when Mitosis is turned on the database need not be rebuilt from scratch.  
> Another work around would be to add a UUID generation tool to add this attribute if replication is to be used but this is a poor work around for the problem.  Question is do you want to deal with the overhead of this UUID attribute for each entry without needing mitosis?  In general it's probably a good idea to have this in effect all the time.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

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

Alex Karasulu updated DIRSERVER-776:
------------------------------------

    Fix Version/s:     (was: 1.5.0)
                   1.5.1

Let's take care of this in 1.5.1.

> entryUUID only created when entries are added with Mitosis enabled
> ------------------------------------------------------------------
>
>                 Key: DIRSERVER-776
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-776
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core, mitosis
>            Reporter: Alex Karasulu
>         Assigned To: Alex Karasulu
>             Fix For: 1.5.1
>
>
> It would be nice to refactor out the UUID injection into standard interceptors so that entries have UUID attributes even if mitosis is not enabled.  This way when Mitosis is turned on the database need not be rebuilt from scratch.  
> Another work around would be to add a UUID generation tool to add this attribute if replication is to be used but this is a poor work around for the problem.  Question is do you want to deal with the overhead of this UUID attribute for each entry without needing mitosis?  In general it's probably a good idea to have this in effect all the time.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/DIRSERVER-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522801 ]

Emmanuel Lecharny commented on DIRSERVER-776:
---------------------------------------------

Status ?

> entryUUID only created when entries are added with Mitosis enabled
> ------------------------------------------------------------------
>
>                 Key: DIRSERVER-776
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-776
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core, mitosis
>            Reporter: Alex Karasulu
>            Assignee: Alex Karasulu
>             Fix For: 1.5.1
>
>
> It would be nice to refactor out the UUID injection into standard interceptors so that entries have UUID attributes even if mitosis is not enabled.  This way when Mitosis is turned on the database need not be rebuilt from scratch.  
> Another work around would be to add a UUID generation tool to add this attribute if replication is to be used but this is a poor work around for the problem.  Question is do you want to deal with the overhead of this UUID attribute for each entry without needing mitosis?  In general it's probably a good idea to have this in effect all the time.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

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

Alex Karasulu updated DIRSERVER-776:
------------------------------------

    Fix Version/s:     (was: 1.5.1)
                   1.5.2

> entryUUID only created when entries are added with Mitosis enabled
> ------------------------------------------------------------------
>
>                 Key: DIRSERVER-776
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-776
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core, mitosis
>            Reporter: Alex Karasulu
>            Assignee: Alex Karasulu
>             Fix For: 1.5.2
>
>
> It would be nice to refactor out the UUID injection into standard interceptors so that entries have UUID attributes even if mitosis is not enabled.  This way when Mitosis is turned on the database need not be rebuilt from scratch.  
> Another work around would be to add a UUID generation tool to add this attribute if replication is to be used but this is a poor work around for the problem.  Question is do you want to deal with the overhead of this UUID attribute for each entry without needing mitosis?  In general it's probably a good idea to have this in effect all the time.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

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

Emmanuel Lecharny updated DIRSERVER-776:
----------------------------------------

    Fix Version/s:     (was: 1.5.2)
                   1.5.3

No status, so postponed

> entryUUID only created when entries are added with Mitosis enabled
> ------------------------------------------------------------------
>
>                 Key: DIRSERVER-776
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-776
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core, mitosis
>            Reporter: Alex Karasulu
>            Assignee: Alex Karasulu
>             Fix For: 1.5.3
>
>
> It would be nice to refactor out the UUID injection into standard interceptors so that entries have UUID attributes even if mitosis is not enabled.  This way when Mitosis is turned on the database need not be rebuilt from scratch.  
> Another work around would be to add a UUID generation tool to add this attribute if replication is to be used but this is a poor work around for the problem.  Question is do you want to deal with the overhead of this UUID attribute for each entry without needing mitosis?  In general it's probably a good idea to have this in effect all the time.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

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

Alex Karasulu updated DIRSERVER-776:
------------------------------------

    Fix Version/s:     (was: 1.5.3)
                   1.5.5

see roadmap

> entryUUID only created when entries are added with Mitosis enabled
> ------------------------------------------------------------------
>
>                 Key: DIRSERVER-776
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-776
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core, mitosis
>            Reporter: Alex Karasulu
>            Assignee: Alex Karasulu
>             Fix For: 1.5.5
>
>
> It would be nice to refactor out the UUID injection into standard interceptors so that entries have UUID attributes even if mitosis is not enabled.  This way when Mitosis is turned on the database need not be rebuilt from scratch.  
> Another work around would be to add a UUID generation tool to add this attribute if replication is to be used but this is a poor work around for the problem.  Question is do you want to deal with the overhead of this UUID attribute for each entry without needing mitosis?  In general it's probably a good idea to have this in effect all the time.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

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

Emmanuel Lecharny updated DIRSERVER-776:
----------------------------------------

    Fix Version/s:     (was: 1.5.5)
                   1.5.7

Moved to 1.5.7, where Mitosis will be reviewed.

> entryUUID only created when entries are added with Mitosis enabled
> ------------------------------------------------------------------
>
>                 Key: DIRSERVER-776
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-776
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core, mitosis
>            Reporter: Alex Karasulu
>            Assignee: Alex Karasulu
>             Fix For: 1.5.7
>
>
> It would be nice to refactor out the UUID injection into standard interceptors so that entries have UUID attributes even if mitosis is not enabled.  This way when Mitosis is turned on the database need not be rebuilt from scratch.  
> Another work around would be to add a UUID generation tool to add this attribute if replication is to be used but this is a poor work around for the problem.  Question is do you want to deal with the overhead of this UUID attribute for each entry without needing mitosis?  In general it's probably a good idea to have this in effect all the time.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

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

Emmanuel Lecharny reassigned DIRSERVER-776:
-------------------------------------------

    Assignee: Emmanuel Lecharny  (was: Alex Karasulu)

> entryUUID only created when entries are added with Mitosis enabled
> ------------------------------------------------------------------
>
>                 Key: DIRSERVER-776
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-776
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core, mitosis
>            Reporter: Alex Karasulu
>            Assignee: Emmanuel Lecharny
>             Fix For: 1.5.7
>
>
> It would be nice to refactor out the UUID injection into standard interceptors so that entries have UUID attributes even if mitosis is not enabled.  This way when Mitosis is turned on the database need not be rebuilt from scratch.  
> Another work around would be to add a UUID generation tool to add this attribute if replication is to be used but this is a poor work around for the problem.  Question is do you want to deal with the overhead of this UUID attribute for each entry without needing mitosis?  In general it's probably a good idea to have this in effect all the time.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/DIRSERVER-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673614#action_12673614 ]

Emmanuel Lecharny commented on DIRSERVER-776:
---------------------------------------------

Moved the UUID injection into the OperationAttributeInterceptor. Still have to determinate which UUID generator we should use.

> entryUUID only created when entries are added with Mitosis enabled
> ------------------------------------------------------------------
>
>                 Key: DIRSERVER-776
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-776
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core, mitosis
>            Reporter: Alex Karasulu
>            Assignee: Emmanuel Lecharny
>             Fix For: 1.5.7
>
>
> It would be nice to refactor out the UUID injection into standard interceptors so that entries have UUID attributes even if mitosis is not enabled.  This way when Mitosis is turned on the database need not be rebuilt from scratch.  
> Another work around would be to add a UUID generation tool to add this attribute if replication is to be used but this is a poor work around for the problem.  Question is do you want to deal with the overhead of this UUID attribute for each entry without needing mitosis?  In general it's probably a good idea to have this in effect all the time.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

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

Emmanuel Lecharny resolved DIRSERVER-776.
-----------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 1.5.7)
                   1.5.5

Fixed in 1.5>.5

> entryUUID only created when entries are added with Mitosis enabled
> ------------------------------------------------------------------
>
>                 Key: DIRSERVER-776
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-776
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core, mitosis
>            Reporter: Alex Karasulu
>            Assignee: Emmanuel Lecharny
>             Fix For: 1.5.5
>
>
> It would be nice to refactor out the UUID injection into standard interceptors so that entries have UUID attributes even if mitosis is not enabled.  This way when Mitosis is turned on the database need not be rebuilt from scratch.  
> Another work around would be to add a UUID generation tool to add this attribute if replication is to be used but this is a poor work around for the problem.  Question is do you want to deal with the overhead of this UUID attribute for each entry without needing mitosis?  In general it's probably a good idea to have this in effect all the time.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[Alex Karasulu-3]

I guess entryUUID is always created now right?  Not just when mitosis is enabled.

Thanks.

On Sat, Jun 13, 2009 at 7:18 PM, Emmanuel Lecharny (JIRA) <jira@...> wrote:

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

Emmanuel Lecharny resolved DIRSERVER-776.
-----------------------------------------

      Resolution: Fixed
   Fix Version/s:     (was: 1.5.7)
                  1.5.5

Fixed in 1.5>.5

> entryUUID only created when entries are added with Mitosis enabled
> ------------------------------------------------------------------
>
>                 Key: DIRSERVER-776
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-776
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core, mitosis
>            Reporter: Alex Karasulu
>            Assignee: Emmanuel Lecharny
>             Fix For: 1.5.5
>
>
> It would be nice to refactor out the UUID injection into standard interceptors so that entries have UUID attributes even if mitosis is not enabled.  This way when Mitosis is turned on the database need not be rebuilt from scratch.
> Another work around would be to add a UUID generation tool to add this attribute if replication is to be used but this is a poor work around for the problem.  Question is do you want to deal with the overhead of this UUID attribute for each entry without needing mitosis?  In general it's probably a good idea to have this in effect all the time.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

--
Alex Karasulu
My Blog :: http://www.jroller.com/akarasulu/
Apache Directory Server :: http://directory.apache.org
Apache MINA :: http://mina.apache.org

[Emmanuel Lecharny]

Alex Karasulu wrote:
> I guess entryUUID is always created now right?  Not just when mitosis is
> enabled.
>  
yes.

--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org