[
https://issues.apache.org/jira/browse/COUCHDB-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671787#comment-13671787
]
Adam Kocoloski commented on COUCHDB-1736:
-----------------------------------------
In my opinion COUCHDB-1735 is superseded by this ticket. If we have an
aliasing system then a rename can be something like an alias creation and
deletion.
In the description on COUCHDB-1735 Dave mentions that the BigCouch code may
complicate this feature addition. I'm biased, but I actually think it provides
a really nice place to implement it. In the BigCouch world every logical
database has a "partition table" that lists the names and locations of the
shard files that comprise it. That partition table is stored as a document in
a special system DB which is replicated to every node in a cluster.
I believe we can implement aliases as partition table documents that either
point to the "canonical" partition table document for the DB (the "ln" option)
or else list the original shard names explicitly (the "cp" option).
Does that make sense?
> Database aliases
> ----------------
>
> Key: COUCHDB-1736
> URL: https://issues.apache.org/jira/browse/COUCHDB-1736
> Project: CouchDB
> Issue Type: Improvement
> Reporter: Dave Cottlehuber
> Labels: couchdb, erlang, gsoc2013
>
> Support redirecting database names at HTTP layer. e.g. GET /foo is passed to
> /bar database internally.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
