Hi Pavan! In my opinion COUCHDB-1735 is superseded by COUCHDB-1736. 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? On May 29, 2013, at 11:23 AM, Pavan Sudheendra <[email protected]> wrote: > Hi all, > > I've been in constant touch with Dave and i'm all set to contribute in some > way or another :) > > I wanted to ask you all about this but couldn't attend the IRC meet today > for some reason. > > I need your input on these bugs. > > 1. https://issues.apache.org/jira/browse/COUCHDB-1736 Database Aliases. > > 2. https://issues.apache.org/jira/browse/COUCHDB-1735 Allow Database > renaming. > > Can you please explain what might be the issues i'd face if i took these > bugs on? > > Database renaming conceptually looks simple, move or copy all the documents > of the database into a seperate view and delete the previous database. Is > there something which i'm missing? I know there is a lot more to this. > Would be glad if someone explained to me how its going to be. > > What about Database Aliases? > > Any help will be greatly appreciated. > -- > Regards- > Pavan
