Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Date: Tue, 17 May 2011 21:01:47 +0000 (UTC)
From: "Emmanuel Lecharny (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Message-ID: 
 <1940742415.20449.1305666107746.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1347432193.19001.1305637367438.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (DIRSERVER-1619) Rdn is not required to be
 stored in ServerEntrySerializer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

True.

Rdn + ParentId in each entry is necessary to rebuild everything from the master table.

Let's do that.

> 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