[GitHub] wohali commented on issue #1155: Cannot access _dbs or _nodes databases through 5984:/_node/

[GitBox <gi...@apache.org>]

wohali commented on issue #1155: Cannot access _dbs or _nodes databases through 5984:/_node/<nodename>
URL: https://github.com/apache/couchdb/issues/1155#issuecomment-364242248
 
 
   Discussion with @rnewson and @chewbranca on IRC lead to the realization that we don't, strictly speaking, need the current `localhost:5986` `/_dbs` `/_nodes` experience over on the public port. Exposing the weirdness that are these two system databases as a "standard" CouchDB database API can lead to confusion over what it really is, which is an auto-magically internally replicating un0sharded local database.
   
   What we need to be able to do is all the things admins typically do with these databases. Here's a partial list off the top of my head:
   * the equivalent of `GET _all_docs`
   * the equivalent of `GET {doc}`
   * the equivalent of `PUT {doc}` (for new docs, or for changed docs)
   * the equivalent of SOMETHING like `_changes`:
     - to be notified when a node is added or changed
     - to be notified when a db is added, or its shard map is changed
       - can we get some/all of this from `_global_changes`?
   * make sure neither `_dbs` nor `_nodes` have any document conflicts (BAD!!!) as a health check
   * shard-level monkeying stuff that needs deeper thought
   
   The ultimate end user goal is to support nice "DBA" scenarios, things like renaming a database in-place without the weight of replication.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services