You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <ji...@apache.org> on 2008/03/20 16:13:24 UTC

[jira] Created: (DIRSTUDIO-304) Allow for specialized operations and inspections on ApacheDS btree partitions

Allow for specialized operations and inspections on ApacheDS btree partitions
-----------------------------------------------------------------------------

                 Key: DIRSTUDIO-304
                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-304
             Project: Directory Studio
          Issue Type: Sub-task
         Environment: all platforms
            Reporter: Alex Karasulu
            Priority: Minor


If we're loading partitions as "pseudo" local connections.  We should be able to expose specialize operations on these partitions via their connections.  For example users might right click on a partition connection, to expose a menu.  Some options will be generally available on all connections.  Some might be connection implementation specific.  

The connection implementation specific options for ApacheDS btree partitions might include the following:

- partition inspector
- add index
- drop index
- rebuild index
- repair
- validate

For example the partition inspector might be a new view that shows the layout of the partition with the contents of the master table, system indices and user indices.  The other operations are shortcuts to operations you might be able to perform within the partition inspector view.  For example add index may create a new user index on the attributeType "ou".  You can imagine the meaning of the other operations which are pretty straight forward.

Now in ApacheDS we have a Maven module called server-tools found here:

    http://svn.apache.org/repos/asf/directory/apacheds/trunk/server-tools/

Some of the operations like add index, or rebuild index will need to be present in CLI based tools.  However the same functionality to perform maintenance on partitions should be in studio as well.  The code can also be shared where the CLI version is just using commons-cli to gather parameters for the command.  Obviously it will be easier and more intuitive for users to use studio instead.



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