directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRSERVER-1619) Rdn is not required to be stored in ServerEntrySerializer
Date Tue, 17 May 2011 20:55:47 GMT

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

Alex Karasulu commented on DIRSERVER-1619:
------------------------------------------

If the aim is to be able to recover everything from the master file then we need to be able
to recover the namespace information encoded inside the Rdn. With just the parent ID we'll
just have hierarchical information (know the structure of the tree entry wise) but we'll loose
the naming information. 

> 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

Mime
View raw message