History | Log In     View a printable version of the current page. Get help!  
Issue Details [XML]

Key: SES-569
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Arjohn Kampman
Reporter: Arjohn Kampman
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Sesame

Sesame Console doesn't remove data dir for dropped repositories

Created: 23/Jun/08 11:29 AM   Updated: 26/Sep/08 11:35 AM
Component/s: Console
Affects Version/s: None
Fix Version/s: 2.2


 Description   
When dropping a repository from the command-line console, the data dir for this repository is not cleaned up. As a result, when creating a repository with the same name afterwards, the new repository will start with the old data.

 All   Comments   Change History      Sort Order:
Comment by Arjohn Kampman [28/Aug/08 10:50 AM]
The Console now uses the functionality provided by the repository managers. Also, a bug in the repository managers was fixed that prevented directory removal for uninitialized repositories.

Comment by Arjohn Kampman [28/Aug/08 10:48 AM]
One can run the 'create' command again to reconfigure a repository. After specifying the (new) configuration parameters, the console will warn you that you're about to overwrite an existing configuration. Simply enter 'yes' to continue doing so.

Comment by Alex Vigdor [25/Jul/08 09:11 PM]
Before implementing this behavior, I would ask that you provide an easy alternative for changing an existing repository configuration without deleting data (e.g. to add an index) - currently the only way that works for me is to drop and re-create the repository, which relies on keeping the data around. Every time I try to directly manipulate the system repository I end up breaking something (the web interface does not reliably allow you to update BNodes) - so if drop is going to delete data, it should be supplemented by a "reconfigure" command to allow configuration changes to existing repositories.