You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Rajesh (JIRA)" <ji...@apache.org> on 2011/05/17 15:02:47 UTC
[jira] [Created] (DIRSERVER-1619) Rdn is not required to be stored
in ServerEntrySerializer
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
[jira] [Commented] (DIRSERVER-1619) Rdn is not required to be
stored in ServerEntrySerializer
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034990#comment-13034990 ]
Alex Karasulu commented on DIRSERVER-1619:
------------------------------------------
Then in that case we're going to have to leave the Rdn in the entry as well. That way the namespace can be reconstructed. Without the Rdn you cannot recover from the master table file alone.
> 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
[jira] [Commented] (DIRSERVER-1619) Rdn is not required to be
stored in ServerEntrySerializer
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (DIRSERVER-1619) Rdn is not required to be
stored in ServerEntrySerializer
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034997#comment-13034997 ]
Alex Karasulu commented on DIRSERVER-1619:
------------------------------------------
Yep on the same page. OK so it makes sense let's keep the Rdn and add the parent ID. That way all is recoverable/reconstructable from the master table.
> 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
[jira] [Commented] (DIRSERVER-1619) Rdn is not required to be
stored in ServerEntrySerializer
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (DIRSERVER-1619) Rdn is not required to be
stored in ServerEntrySerializer
Posted by "Stefan Seelmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034902#comment-13034902 ]
Stefan Seelmann commented on DIRSERVER-1619:
--------------------------------------------
I think it is worth to keep the RDN (and additionally add the parent ID) in the entry which is stored in the master table. This way the master table would be the authoritative source and would contain all data required to rebuild the indices, including the RDN index.
> 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
[jira] [Commented] (DIRSERVER-1619) Rdn is not required to be
stored in ServerEntrySerializer
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (DIRSERVER-1619) Rdn is not required to be
stored in ServerEntrySerializer
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034804#comment-13034804 ]
Emmanuel Lecharny commented on DIRSERVER-1619:
----------------------------------------------
As usual, export the LDIF entries and reimport them.
> 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
[jira] [Resolved] (DIRSERVER-1619) Rdn is not required to be stored
in ServerEntrySerializer
Posted by "Kiran Ayyagari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kiran Ayyagari resolved DIRSERVER-1619.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.0-M1
Assignee: Kiran Ayyagari
Have fixed this here http://svn.apache.org/viewvc?rev=1104280&view=rev .
So far no regression found and the test suits are passing. Thanks for reporting.
> 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
[jira] [Commented] (DIRSERVER-1619) Rdn is not required to be
stored in ServerEntrySerializer
Posted by "Kiran Ayyagari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041499#comment-13041499 ]
Kiran Ayyagari commented on DIRSERVER-1619:
-------------------------------------------
Fixed here http://svn.apache.org/viewvc?rev=1129250&view=rev
> 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.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
[jira] [Commented] (DIRSERVER-1619) Rdn is not required to be
stored in ServerEntrySerializer
Posted by "Kiran Ayyagari (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (DIRSERVER-1619) Rdn is not required to be
stored in ServerEntrySerializer
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034944#comment-13034944 ]
Alex Karasulu commented on DIRSERVER-1619:
------------------------------------------
Initially I thought putting the parent ID into the entry might be problematic for move's of entire subtrees causing several master table accesses. However this is not the case. The access will occur just on the node being moved and not on it's descendants. So this is a "safe" idea but what benefits were you thinking of when deciding to include the parent ID in the Entry?
> 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
[jira] [Commented] (DIRSERVER-1619) Rdn is not required to be
stored in ServerEntrySerializer
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034995#comment-13034995 ]
Emmanuel Lecharny commented on DIRSERVER-1619:
----------------------------------------------
As Kiran said, keeping the RDN in the entry does not help without the entry parent's ID, so better just have the parent's iD
If we decide to inject the Parent ID in the entry, then we will be safe. A move operation will just impact the moved entry. It's a free operation.
> 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
[jira] [Commented] (DIRSERVER-1619) Rdn is not required to be
stored in ServerEntrySerializer
Posted by "Kiran Ayyagari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034803#comment-13034803 ]
Kiran Ayyagari commented on DIRSERVER-1619:
-------------------------------------------
No, entries need to be manually imported into the new database.
> 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
[jira] [Commented] (DIRSERVER-1619) Rdn is not required to be
stored in ServerEntrySerializer
Posted by "Kiran Ayyagari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034986#comment-13034986 ]
Kiran Ayyagari commented on DIRSERVER-1619:
-------------------------------------------
Seelmann's recommendation is valid and IMO very important to consider from recovery pov. This makes recovery very easy with just master table alone.
But in order to achieve this we must include the parent's ID as an operational attribute inside the Entry, otherwise there is no easy way that
the serialization layer has access to the Entry's parent ID.
> 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
[jira] [Commented] (DIRSERVER-1619) Rdn is not required to be
stored in ServerEntrySerializer
Posted by "Rajesh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034799#comment-13034799 ]
Rajesh commented on DIRSERVER-1619:
-----------------------------------
Will the database be upgraded automatically when users switch to new version? Otherwise old entries may still have the Rdn and the database loading will not work.
> 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
[jira] [Commented] (DIRSERVER-1619) Rdn is not required to be
stored in ServerEntrySerializer
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035018#comment-13035018 ]
Emmanuel Lecharny commented on DIRSERVER-1619:
----------------------------------------------
Hmmm, why do we have to keep the RDN ? Isn't it enough to store the RDN id instead ? (not the parent ID)
> 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
[jira] [Commented] (DIRSERVER-1619) Rdn is not required to be
stored in ServerEntrySerializer
Posted by "Kiran Ayyagari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034993#comment-13034993 ]
Kiran Ayyagari commented on DIRSERVER-1619:
-------------------------------------------
Right, but unless we store the parent ID, having RDN alone in the Entry won't be helpful.
> 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
[jira] [Commented] (DIRSERVER-1619) Rdn is not required to be
stored in ServerEntrySerializer
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034757#comment-13034757 ]
Emmanuel Lecharny commented on DIRSERVER-1619:
----------------------------------------------
IMO, the best thing would be to get rid of the RDN serialization, and see where the server explodes, if it does :)
> 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