[
https://issues.apache.org/jira/browse/DIRSERVER-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034755#comment-13034755
]
Kiran Ayyagari commented on DIRSERVER-1619:
-------------------------------------------
This is a very valid observation, we can do this optimization BUT I can't
recollect why exactly I have kept the RDN in the Entry while implementing the
RdnIndex. Am trying to find it, but haven't found anything tangible so far.
> 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
> Priority: Minor
>
> 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
