[ https://issues.apache.org/jira/brow...ls:all-tabpanel ]

Alex Karasulu updated DIRSERVER-465:
------------------------------------

Priority: Critical  (was: Minor)

This is critical for ease of use.

> Use multiple PartitionNexus' for layered partitioning
> -----------------------------------------------------
>
>                 Key: DIRSERVER-465
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-465
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>          Components: core
>            Reporter: Alex Karasulu
>            Assignee: Alex Karasulu
>            Priority: Critical
>             Fix For: bigbang
>
>
> I just got a great idea but it might be a little crazy.  There is a problem with t
he current model where there can only be one (singleton) nexus way at the top of a s
ystem.  This severly limits how the namespace can be partitioned.  Because of Backin
gSt
ore operation routing concerns to ContextPartitions, one cannot have two ContextPartitions h
aving a suffix overlap.  Basically ContextPartitions with suffixes like so are not allowed:[
vbcol=seagreen]
> ..o CP1 suffix is dc=apache,dc=org
> ..o CP2 suffix is ou=people,dc=apache,dc=org
> Here's how the tree might look:
> .............................[RootNexus]
> ................................/...\
> ............................[CP1]...[CP2]
> The suffix of CP1 overlaps the suffix of CP2.  Basically requests recieved
 under the CP2 suffix base have a tough time determining where they should r
oute calls.  To avoid this confusion there is the restriction mentioned abov
e.
> What if had a very special kind of nexus that was not a singleton and had a suffix
 associated with it?  Furthermore this nexus can contain entries off of that suffix 
as well instead of just delagating their storage to partitions it bridges.  This nex
us[/vbcol]
could then eliminate the routing problem and remove the restriction.  For the time being let
s call this a ContextNexus.  So we could have the following configuration:
> ..o CN1 suffix is dc=apache,dc=org
> ..o CP2 suffix is ou=people,dc=apache,dc=org
> Here's how the tree might look:
> .............................[RootNexus]
> ..................................|
> ................................[CN1]
> ..................................|
> ................................[CP2]
> Here in this case entries like ou=groups,dc=apache,dc=apache and its contents woul
d be stored in CN1 and so would the suffix dc=apache,dc=org.  Now because of this ex
tra level of routing decisions for routing cannot get confusing.   We can then parti
tio
n the namespace in any manner we see fit with minimal cost to performance.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[ Post a follow-up to this message ]