You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@couchdb.apache.org by "Alexander Shorin (JIRA)" <ji...@apache.org> on 2015/02/23 22:05:12 UTC

[jira] [Updated] (COUCHDB-2620) Rename cassim db to _metadata

     [ https://issues.apache.org/jira/browse/COUCHDB-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Shorin updated COUCHDB-2620:
--------------------------------------
    Description: After IRC conversation with [~janl] and [~chewbranca] we -decided- are proposing to rename cassim database into something more specific and concrete. This database currently holds only _security of all cluster databases, but is designed for more. In future, we could use it to handle config-per-database feature and etc. The _metadata name reflects nicely such propose.  (was: After IRC conversation with [~janl] and [~chewbranca] we decided to rename cassim database into something more specific and concrete. This database currently holds only _security of all cluster databases, but is designed for more. In future, we could use it to handle config-per-database feature and etc. The _metadata name reflects nicely such propose.)

> Rename cassim db to _metadata
> -----------------------------
>
>                 Key: COUCHDB-2620
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2620
>             Project: CouchDB
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Database Core
>            Reporter: Alexander Shorin
>
> After IRC conversation with [~janl] and [~chewbranca] we -decided- are proposing to rename cassim database into something more specific and concrete. This database currently holds only _security of all cluster databases, but is designed for more. In future, we could use it to handle config-per-database feature and etc. The _metadata name reflects nicely such propose.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)