couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Kocoloski (JIRA)" <>
Subject [jira] Commented: (COUCHDB-355) deleting a _config key sets the value to ""
Date Sun, 19 Jul 2009 20:05:15 GMT


Adam Kocoloski commented on COUCHDB-355:

This bug is complicated by our use of configuration directories.  At the moment runtime updates
to the configuration are persisted in the last file in the config chain.  If the config KV
we want to delete is in another file we're going to have trouble finding it.

> deleting a _config key sets the value to ""
> -------------------------------------------
>                 Key: COUCHDB-355
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>    Affects Versions: 0.9
>            Reporter: Adam Kocoloski
>            Assignee: Adam Kocoloski
> couch_config:delete/2 is implemented as
> delete(Section, Key) ->
>     set(Section, Key, "").
> I think that's misleading -- a key with an empty value is not the same as no key at all.
 Consider the case of an update_notification process.  To me, deleting that key should just
send an EOF to the process.  Instead Couch sends the EOF and then tries to spawn an os_process
to execute "".  The end result is the same, but a few things crash along the way.

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

View raw message