[
https://issues.apache.org/jira/browse/COUCHDB-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830847#action_12830847
]
Juhani Ränkimies commented on COUCHDB-86:
-----------------------------------------
Sorry about the sloppy patch,
Some of those are already addressed in the branch
http://github.com/juranki/couchdb/commits/windows_compact_2
* force_close_file is already cleaned
* I agree that couch_file:delete is dangerous as is. I'll look into that.
* I'll change delete_all -> delete_all_versions
* I'll move the 'EXIT' handling to a separate process
I haven't yet nailed what's with the changes test; changes api seems to work
when playing with python client.
There was also a bug with couch_file:delete_all error reporting; it caused the
{"error":"file_exists","reason":"The database could not be created, the file
already exists."} .
> (CouchDB on Windows) compaction can not be done.
> ------------------------------------------------
>
> Key: COUCHDB-86
> URL: https://issues.apache.org/jira/browse/COUCHDB-86
> Project: CouchDB
> Issue Type: Bug
> Components: Build System
> Affects Versions: 0.8
> Environment: Windows XP, Erlang/OTP R12B-3
> Reporter: Li Zhengji
> Assignee: Paul Joseph Davis
> Priority: Blocker
> Fix For: 1.0
>
> Original Estimate: 5h
> Remaining Estimate: 5h
>
> During compacting, rename the current DB file to a .old file is not allowed
> on Windows.
> A possible workaround for this could be:
> 1. Close current DB file (.couch);
> 2. Send db_updated to update to use .compact;
> 3. After 5sec, delete the .couch file; ---- This is done in a linked
> process, after that, this process send a message to update_loop;
> 4. After received the message in update_loop, close current DB file which is
> a .compact file, then rename it to .couch;
> 5. Finally, db_updated again to use this new .couch file.
> Maybe, there would be a "pause" in service?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.