You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Randy Motluck (JIRA)" <ji...@apache.org> on 2007/08/28 01:27:30 UTC

[jira] Created: (DIRSERVER-1036) Change backend to allow alternate store configurations - not just non-jdbm

Change backend to allow alternate store configurations - not just non-jdbm
--------------------------------------------------------------------------

                 Key: DIRSERVER-1036
                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1036
             Project: Directory ApacheDS
          Issue Type: New Feature
         Environment: All
            Reporter: Randy Motluck


Re-factor back end to allow non-jdbm partitions -- SQL DB, Proxy and Aggregator Back ends.
Back end could be a single store (JDBM, SQL DB), proxy (or proxies) to other LDAP server(s), or a combination (aggregator).

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


[jira] Commented: (DIRSERVER-1036) Change backend to allow alternate store configurations - not just non-jdbm

Posted by "Bryce Nordgren (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DIRSERVER-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763610#action_12763610 ] 

Bryce Nordgren commented on DIRSERVER-1036:
-------------------------------------------

Is there a prototype of this functionality in SVN?  I could use it today for LDAP authentication off of a corporate Active Directory source + my own local additions merged into a single view.  I'm far from an expert, but the O'reilly LDAP admin book terms this a "metadirectory".  

> Change backend to allow alternate store configurations - not just non-jdbm
> --------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1036
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1036
>             Project: Directory ApacheDS
>          Issue Type: New Feature
>         Environment: All
>            Reporter: Randy Motluck
>             Fix For: 2.0.0
>
>
> Re-factor back end to allow non-jdbm partitions -- SQL DB, Proxy and Aggregator Back ends.
> Back end could be a single store (JDBM, SQL DB), proxy (or proxies) to other LDAP server(s), or a combination (aggregator).

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


[jira] Updated: (DIRSERVER-1036) Change backend to allow alternate store configurations - not just non-jdbm

Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny updated DIRSERVER-1036:
-----------------------------------------

    Fix Version/s: 2.0.0

Will be fixed in 2.0

> Change backend to allow alternate store configurations - not just non-jdbm
> --------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1036
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1036
>             Project: Directory ApacheDS
>          Issue Type: New Feature
>         Environment: All
>            Reporter: Randy Motluck
>             Fix For: 2.0.0
>
>
> Re-factor back end to allow non-jdbm partitions -- SQL DB, Proxy and Aggregator Back ends.
> Back end could be a single store (JDBM, SQL DB), proxy (or proxies) to other LDAP server(s), or a combination (aggregator).

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


[jira] Resolved: (DIRSERVER-1036) Change backend to allow alternate store configurations - not just non-jdbm

Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny resolved DIRSERVER-1036.
------------------------------------------

    Resolution: Fixed

The new API now supports any type of backend. So far, beside JDBM, we are able to manage LDIF backend, In Memory, Oracle and HBase.

> Change backend to allow alternate store configurations - not just non-jdbm
> --------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1036
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1036
>             Project: Directory ApacheDS
>          Issue Type: New Feature
>         Environment: All
>            Reporter: Randy Motluck
>             Fix For: 2.0.0-RC1
>
>
> Re-factor back end to allow non-jdbm partitions -- SQL DB, Proxy and Aggregator Back ends.
> Back end could be a single store (JDBM, SQL DB), proxy (or proxies) to other LDAP server(s), or a combination (aggregator).

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


[jira] Updated: (DIRSERVER-1036) Change backend to allow alternate store configurations - not just non-jdbm

Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny updated DIRSERVER-1036:
-----------------------------------------

    Fix Version/s: 2.0.0-RC1
                       (was: 2.0.0)

Moved back to 2.0.0-RC1

> Change backend to allow alternate store configurations - not just non-jdbm
> --------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1036
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1036
>             Project: Directory ApacheDS
>          Issue Type: New Feature
>         Environment: All
>            Reporter: Randy Motluck
>             Fix For: 2.0.0-RC1
>
>
> Re-factor back end to allow non-jdbm partitions -- SQL DB, Proxy and Aggregator Back ends.
> Back end could be a single store (JDBM, SQL DB), proxy (or proxies) to other LDAP server(s), or a combination (aggregator).

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