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

Emmanuel Lecharny commented on DIRSERVER-1619:
----------------------------------------------

Sadly, even if you keep the RDN in the Master table, you still need the RDN table to rebuild the whole base : the RDN only gives you no clue about where in the DIT the entry belongs to.

Two entries may have the exact same RDN in two places.

> Rdn is not required to be stored in ServerEntrySerializer
> ---------------------------------------------------------
>
>                 Key: DIRSERVER-1619
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1619
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.5.7
>            Reporter: Rajesh
>            Assignee: Kiran Ayyagari
>            Priority: Minor
>             Fix For: 2.0-M1
>
>
> In ServerEntrySerializer Rdn is also being serialzied. And when we are trying to lookup Entry from the AbstractTable, we are not using the Rdn or even the Entry to construct the Dn. Dn is being constructed using Rdn Table. 
> So it will improve performance a bit if we don't save the Rdn at all.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira