<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 02:54:55 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[SERVER-701] Ability to rename databases</title>
                <link>https://jira.mongodb.org/browse/SERVER-701</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;div class=&quot;panel&quot; style=&quot;background-color: #eeeeee;border-color: #cccccc;border-width: 1px;&quot;&gt;&lt;div class=&quot;panelHeader&quot; style=&quot;border-bottom-width: 1px;border-bottom-color: #cccccc;background-color: #6cb33f;&quot;&gt;&lt;b&gt;Issue Status as of Apr 9, 2015&lt;/b&gt;&lt;/div&gt;&lt;div class=&quot;panelContent&quot; style=&quot;background-color: #eeeeee;&quot;&gt;
&lt;p&gt;&lt;b&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;UPDATE Sep 10, 2019&amp;#93;&lt;/span&gt;&lt;/b&gt;&#160; &lt;br/&gt;
The&#160;&quot;copydb&quot; command is deprecated, please use these two commands instead: &lt;br/&gt;
 &#160; &#160; 1. &lt;a href=&quot;https://docs.mongodb.com/manual/reference/program/mongodump/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;mongodump&lt;/a&gt; (to back up data) &lt;br/&gt;
 &#160; &#160; 2. &lt;a href=&quot;https://docs.mongodb.com/manual/reference/program/mongorestore/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;mongorestore&lt;/a&gt; (to recover data from mongodump into a new namespace)&lt;/p&gt;

&lt;p&gt;&lt;b&gt;----------------------&#160;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;We are aware of how painful and long it is to rename a database in MongoDB. Unfortunately, this is not an simple feature for us to implement due to the way that database metadata is stored in the original (default) storage engine. In MMAPv1 files, the namespace (e.g.: dbName.collection) that describes every single collection and index includes the database name, so to rename a set of database files, every single namespace string would have to be rewritten. This impacts:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;the .ns file&lt;/li&gt;
	&lt;li&gt;every single numbered file for the collection&lt;/li&gt;
	&lt;li&gt;the namespace for every index&lt;/li&gt;
	&lt;li&gt;internal unique names of each collection and index&lt;/li&gt;
	&lt;li&gt;contents of system.namespaces and system.indexes (or their equivalents in the future)&lt;/li&gt;
	&lt;li&gt;other locations I may be missing&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;This is just to accomplish a rename of a single database in a &lt;b&gt;standalone&lt;/b&gt; mongod instance. For replica sets the above would need to be done on every replica node, plus on each node every single oplog entry that refers this database would have to be somehow invalidated or rewritten, and then if it&apos;s a sharded cluster, one also needs to add these changes to every shard if the DB is sharded, plus the config servers have all the shard metadata in terms of namespaces with their full names.&lt;/p&gt;

&lt;p&gt;There would be absolutely no way to do this on a live system.&lt;/p&gt;

&lt;p&gt;To do it offline, it would require re-writing every single database file to accommodate the new name,&#160;and at that point it would be as slow as the current &quot;copydb&quot; command.&lt;/p&gt;

&lt;p&gt;Asya Kamsky,&lt;br/&gt;
MongoDB Product Team&lt;/p&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;h6&gt;&lt;a name=&quot;Originaldescription&quot;&gt;&lt;/a&gt;Original description&lt;/h6&gt;
&lt;p&gt;Having the ability to rename databases would be nice.  That would allow things like cloning a database with straight file copies plus a rename (to avoid having to wait on index builds when using db.copyDatabase).&lt;/p&gt;</description>
                <environment></environment>
        <key id="11424">SERVER-701</key>
            <summary>Ability to rename databases</summary>
                <type id="2" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14711&amp;avatarType=issuetype">New Feature</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="10038" iconUrl="https://jira.mongodb.org/images/icons/subtask.gif" description="">Backlog</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="brian.lane@mongodb.com">Brian Lane</assignee>
                                    <reporter username="ejones">Erik Jones</reporter>
                        <labels>
                    </labels>
                <created>Thu, 4 Mar 2010 18:13:20 +0000</created>
                <updated>Thu, 6 Apr 2023 18:54:30 +0000</updated>
                                                                            <component>Usability</component>
                                        <votes>210</votes>
                                    <watches>154</watches>
                                                                                                                <comments>
                            <comment id="4539970" author="steven.vannelli" created="Tue, 10 May 2022 21:31:55 +0000"  >&lt;p&gt;Moving this ticket to the Backlog and removing the &quot;Backlog&quot; fixVersion as per our latest policy for using fixVersions. &lt;/p&gt;</comment>
                            <comment id="2412248" author="brian.lane" created="Mon, 9 Sep 2019 07:04:54 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=amcgregor&quot; class=&quot;user-hover&quot; rel=&quot;amcgregor&quot;&gt;amcgregor&lt;/a&gt;,&lt;/p&gt;

&lt;p&gt;Thanks for the feedback.    I have created &lt;a href=&quot;https://jira.mongodb.org/browse/DOCS-13024&quot; title=&quot;Surface namespace rename example in assertion from copyDatabase deprecation link&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DOCS-13024&quot;&gt;&lt;del&gt;DOCS-13024&lt;/del&gt;&lt;/a&gt; based on your comment.&lt;/p&gt;

&lt;p&gt;Feel free to comment on &lt;a href=&quot;https://jira.mongodb.org/browse/DOCS-13024&quot; title=&quot;Surface namespace rename example in assertion from copyDatabase deprecation link&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DOCS-13024&quot;&gt;&lt;del&gt;DOCS-13024&lt;/del&gt;&lt;/a&gt; in case I may have missed anything.&lt;/p&gt;

&lt;p&gt;-Brian&lt;/p&gt;</comment>
                            <comment id="2409300" author="alice@gothcandy.com" created="Thu, 5 Sep 2019 17:15:44 +0000"  >&lt;p&gt;The initial recommendation in the absence of the ability to rename (for technical reasons which are &lt;em&gt;entirely solvable with a &lt;tt&gt;for&lt;/tt&gt; loop&lt;/em&gt;&#8230;) to use &lt;tt&gt;copyDatabase&lt;/tt&gt; is problematic. Given &lt;tt&gt;copyDatabase&lt;/tt&gt; has been hard-deprecated. (&lt;em&gt;Hard&lt;/em&gt; as in: &lt;b&gt;it no longer works&lt;/b&gt;, even with a warning; it fails with an assertion error.)&lt;/p&gt;

&lt;p&gt;What&apos;s particularly worse is that while the assertion provides a link to the relevant change log, &lt;a href=&quot;https://docs.mongodb.com/manual/release-notes/4.0-compatibility/#copydb-and-clone-commands&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;that change log&lt;/a&gt; makes a recommendation that it does not follow through with an example. Use &lt;tt&gt;mongodump&lt;/tt&gt; and &lt;tt&gt;mongorestore&lt;/tt&gt;! I&apos;d love to. How? Given I have BSON files exported to directory-per-db &lt;b&gt;and&lt;/b&gt; &lt;tt&gt;--gzip --archive&lt;/tt&gt; backups, and attempting to use the {-d} option to target an alternate database issues:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;the --db and --collection args should only be used when restoring from a BSON file. Other uses are deprecated and will not exist in the future; use --nsInclude instead&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;C&apos;mon, now. That suggestion / recommendation is outlandish when I&apos;m not attempting to filter which database or collections are restored, I&apos;m only trying to specify the destination database to populate. &#160;(This message &lt;em&gt;might&lt;/em&gt; make sense during &lt;tt&gt;mongodump&lt;/tt&gt;, where you probably are trying to filter, but not on restore.) &#160;Which, after deeper investigation, should utilize &lt;tt&gt;nsFrom&lt;/tt&gt; and &lt;tt&gt;nsTo&lt;/tt&gt;, no? Thus the change log should point developers at the &lt;a href=&quot;https://docs.mongodb.com/manual/reference/program/mongorestore/#example-complex-wildcard-usage&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;mongorestore reference &quot;recipe&quot; for &quot;Change Collections&apos; Namespaces during Restore&quot;&lt;/a&gt;, specifically. &#160;Or, even better, provide a concrete equivalent example to the old process.&lt;/p&gt;</comment>
                            <comment id="2175361" author="airs0urce" created="Fri, 8 Mar 2019 01:09:22 +0000"  >&lt;p&gt;It takes a long time to move collection by collection in new database. Would be good to get ability to rename DB without copying all the data around.&lt;/p&gt;</comment>
                            <comment id="1951992" author="brezniczky@gmail.com" created="Fri, 20 Jul 2018 06:12:38 +0000"  >&lt;p&gt;Again (and again) a year gone - any news perhaps?&lt;/p&gt;</comment>
                            <comment id="1712949" author="ygbr@mac.com" created="Mon, 30 Oct 2017 20:43:08 +0000"  >&lt;p&gt;Any news on this for wiredtiger on MongoDB 3.4+ ?&lt;/p&gt;</comment>
                            <comment id="1199307" author="hu.sesselmann@dsfishlabs.com" created="Thu, 10 Mar 2016 17:41:43 +0000"  >&lt;p&gt;Almost a year has passed - are there any news on this topic? &lt;img class=&quot;emoticon&quot; src=&quot;https://jira.mongodb.org/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;</comment>
                            <comment id="877132" author="asya" created="Thu, 9 Apr 2015 15:46:48 +0000"  >&lt;p&gt;Hi Alex,&lt;/p&gt;

&lt;p&gt;WredTiger storage engine fortunately keeps the metadata only in limited number of places.   However, we support (and encourage) migration between storage engines via the replica set, by being able to run different storage engines on different nodes.  We basically make a promise that any operation you perform on the primary will be able to replicate successfully to the other members.&lt;/p&gt;

&lt;p&gt;Having said that, we are considering the future and what the implications of supporting a command that would not work on all the storage engines would be.  As you might imagine, we have to be extremely careful around this, so as not to break things unexpectedly.   In addition, we are very hesitant to add support for any commands which work on some configurations and don&apos;t on others (for example, we really want to make sure that we never add new commands that only work &quot;unsharded&quot; and then break when you move to a sharded cluster).&lt;/p&gt;

&lt;p&gt;Asya&lt;/p&gt;</comment>
                            <comment id="877094" author="mobafill" created="Thu, 9 Apr 2015 15:20:54 +0000"  >&lt;p&gt;Hi Asya, &lt;/p&gt;

&lt;p&gt;thanks for detailed answer. &lt;/p&gt;

&lt;p&gt;That&apos;s unfortunate but understandable, however, what about WiredTiger storage?&lt;/p&gt;

&lt;p&gt;Regards&lt;br/&gt;
Alex.&lt;/p&gt;</comment>
                            <comment id="877067" author="asya" created="Thu, 9 Apr 2015 15:05:33 +0000"  >&lt;p&gt;Folks,&lt;/p&gt;

&lt;p&gt;We are aware of how painful and long it is to rename a database in MongoDB. Unfortunately, this is not an simple feature for us to implement due to the way that database metadata is stored in the original (default) storage engine. In MMAPv1 files, the namespace (e.g.: dbName.collection) that describes every single collection and index includes the database name, so to rename a set of database files, every single namespace string would have to be rewritten. This impacts:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;the .ns file&lt;/li&gt;
	&lt;li&gt;every single numbered file for the collection&lt;/li&gt;
	&lt;li&gt;the namespace for every index&lt;/li&gt;
	&lt;li&gt;internal unique names of each collection and index&lt;/li&gt;
	&lt;li&gt;contents of system.namespaces and system.indexes (or their equivalents in the future)&lt;/li&gt;
	&lt;li&gt;other locations I may be missing&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;This is just to accomplish a rename of a single database in a &lt;b&gt;standalone&lt;/b&gt; mongod instance. For replica sets the above would need to be done on every replica node, plus on each node every single oplog entry that refers this database would have to be somehow invalidated or rewritten, and then if it&apos;s a sharded cluster, one also needs to add these changes to every shard if the DB is sharded, plus the config servers have all the shard metadata in terms of namespaces with their full names.&lt;/p&gt;

&lt;p&gt;There would be absolutely no way to do this on a live system. &lt;/p&gt;

&lt;p&gt;To do it offline, it would require re-writing every single database file to accommodate the new name, and at that point it would be as slow as the current &quot;copydb&quot; command.&lt;/p&gt;

&lt;p&gt;Asya Kamsky,&lt;br/&gt;
MongoDB Product Team&lt;/p&gt;</comment>
                            <comment id="874057" author="alecyu" created="Mon, 6 Apr 2015 22:19:45 +0000"  >&lt;p&gt;My manager is asking to moving out from mongo because of this (the major reason)&lt;/p&gt;</comment>
                            <comment id="874033" author="farquaad" created="Mon, 6 Apr 2015 21:54:24 +0000"  >&lt;p&gt;Seriously this is classified as minor feature?!!! I am currently evaluating MongoDB for one of my clients, and, in all fairness, cannot recommend it as mature product with such basic functionality missing.&lt;/p&gt;</comment>
                            <comment id="847714" author="legel" created="Tue, 10 Mar 2015 16:50:32 +0000"  >&lt;p&gt;Pretty ridiculous that a simple functionality like this is not provided...&lt;/p&gt;</comment>
                            <comment id="840015" author="mobafill" created="Mon, 2 Mar 2015 10:13:43 +0000"  >&lt;p&gt;I&apos;m writing again here (already upvoted) to confirm that we still need this. I&apos;ve managed to rename one problematic database and it was a real pain to do that. I will not dare to do this on the second one as it&apos;s few terabytes large and it will take ages. &lt;br/&gt;
A way to easily rename databases regardless of it&apos;s size is urgently required.&lt;/p&gt;

&lt;p&gt;Philosophy of NoSQL in general and MongoDB particularly is about moving quickly without thorough long-term planning, allowing early mistakes and allowing to easily fix them later when you know what your architecture actually is. Not being able to easily fix database naming is not only a nuisance and a bugger, it&apos;s a major system inconsistency and goes across Mongo&apos;s &quot;Flexible Data Model&quot; mission statement. Being unable to rename database is not a flexible data model.&lt;/p&gt;</comment>
                            <comment id="840000" author="andrey.hohutkin@gmail.com" created="Mon, 2 Mar 2015 09:47:23 +0000"  >&lt;p&gt;It is urgent feature. Extremely needed for DB maintenance.&lt;/p&gt;</comment>
                            <comment id="829953" author="sunnybg" created="Mon, 16 Feb 2015 15:46:19 +0000"  >&lt;p&gt;How many votes are enough for this to be considered?&lt;/p&gt;</comment>
                            <comment id="807553" author="mobafill" created="Mon, 19 Jan 2015 11:25:45 +0000"  >&lt;p&gt;Upvoted. I need to rename two databases right now, due to early project mistakes that now causing terms confusion. And seems like there is no easy way to do that. &lt;/p&gt;</comment>
                            <comment id="789551" author="jlyonsmith" created="Thu, 18 Dec 2014 16:24:46 +0000"  >&lt;p&gt;Hello!  Anybody in there...?  Pretty please?&lt;/p&gt;</comment>
                            <comment id="781385" author="guillermo85" created="Mon, 8 Dec 2014 23:59:05 +0000"  >&lt;p&gt;Please add this feature, a future database server must rename his databases. Thanks!&lt;/p&gt;</comment>
                            <comment id="773925" author="alecyu" created="Thu, 27 Nov 2014 08:25:07 +0000"  >&lt;p&gt;I&apos;ve needed this features.&lt;br/&gt;
thanks&lt;/p&gt;</comment>
                            <comment id="762305" author="rob_colella@volusion.com" created="Wed, 12 Nov 2014 16:09:57 +0000"  >&lt;p&gt;Please add this feature as it is critical and should be standard in an enterprise environment. &lt;/p&gt;</comment>
                            <comment id="738458" author="sherryummen" created="Fri, 10 Oct 2014 10:54:12 +0000"  >&lt;p&gt;so with my vote we have 150 votes; could this feature be considered in near future please. Or atleast an efficient workaround, rather we always copy everything? I am using C# Driver where _server.CopyDatabase() is also Obselete.&lt;/p&gt;</comment>
                            <comment id="627242" author="kreig" created="Thu, 19 Jun 2014 08:58:40 +0000"  >&lt;p&gt;Please implement this feature. It would save a lot of time not only for production environment. It takes realy a lot of time to restore databse from production backup, devs would be much happier with such handy command.&lt;/p&gt;</comment>
                            <comment id="513990" author="djvw@redscreen.co.za" created="Wed, 12 Mar 2014 04:51:55 +0000"  >&lt;p&gt;Very good point @Dan_Dascalescu. I would hate to see what our maintenance guys think when you copy that much data in a production environment.&lt;/p&gt;</comment>
                            <comment id="511381" author="dandv" created="Fri, 7 Mar 2014 10:48:05 +0000"  >&lt;p&gt;Adding my voice to this. I would much rather have a &quot;rename&quot; function, than having to wait for db.copyDatabase() to complete on my 2TB database.&lt;/p&gt;

&lt;p&gt;Not to mention that you might not have enough disk space for two copies of your database, or you might needlessly pay for it.&lt;/p&gt;</comment>
                            <comment id="462018" author="rgpublic" created="Tue, 26 Nov 2013 15:41:44 +0000"  >&lt;p&gt;@Ilya: According to this (&lt;a href=&quot;http://stackoverflow.com/questions/15303409/how-to-rename-a-database-using-mongomapper-in-ruby&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://stackoverflow.com/questions/15303409/how-to-rename-a-database-using-mongomapper-in-ruby&lt;/a&gt;) the db.rename Funktion is only a shell-specific wrapper for copyDatabase/dropDatabase. A real &quot;rename&quot; like proposed in this JIRA ticket doesn&apos;t exist yet.&lt;/p&gt;</comment>
                            <comment id="462010" author="diversario" created="Tue, 26 Nov 2013 15:29:16 +0000"  >&lt;p&gt;How come that in the shell I can say &lt;tt&gt;db.rename(&apos;newname&apos;)&lt;/tt&gt; and it works but I cannot do the same in the mongo shell script?&lt;/p&gt;</comment>
                            <comment id="438361" author="nwerneck" created="Wed, 9 Oct 2013 19:13:37 +0000"  >&lt;p&gt;I would like not just renaming, but also creating an &quot;alias&quot; would be nice. So for example we can have multiple dumps from some database with different names (their dates), but then have an alias that points to the most recent of them...&lt;/p&gt;</comment>
                            <comment id="419992" author="hedefalk" created="Sat, 7 Sep 2013 08:58:17 +0000"  >&lt;p&gt;+1&lt;/p&gt;</comment>
                            <comment id="405889" author="zugwalt" created="Mon, 19 Aug 2013 00:32:08 +0000"  >&lt;p&gt;Renaming would be great for large databases&lt;/p&gt;</comment>
                            <comment id="350138" author="kmehta" created="Fri, 31 May 2013 19:37:45 +0000"  >&lt;p&gt;+1 Please add this feature! I get a monthly dataset and was hoping to slide my datasets to preserve historical data. I&apos;m shocked this isn&apos;t supported. We really need this. Thanks.&lt;/p&gt;</comment>
                            <comment id="350109" author="justin@idle-games.com" created="Fri, 31 May 2013 18:53:24 +0000"  >&lt;p&gt;+1&lt;/p&gt;

&lt;p&gt;I&apos;ll add that the ability to do this while the server is down would be sufficient for my needs. I would think/hope that this should be as simple as renaming the files on the filesystem and updating some kind of internal metadata. A workaround or hack until the online in-server feature is finished would be acceptable.&lt;/p&gt;

&lt;p&gt;I have already implemented all sorts of what I see as hacks when restoring a sharded cluster. I have to manually update all sorts of metadata in the config db to make a restored cluster work, even without renaming databases.&lt;/p&gt;</comment>
                            <comment id="332856" author="amey.potnis@gmail.com" created="Fri, 10 May 2013 15:54:49 +0000"  >&lt;p&gt;+1&lt;/p&gt;</comment>
                            <comment id="323131" author="anupk" created="Sat, 27 Apr 2013 20:26:12 +0000"  >&lt;p&gt;+1&lt;/p&gt;</comment>
                            <comment id="306071" author="bkonash@squarespace.com" created="Thu, 4 Apr 2013 18:07:40 +0000"  >&lt;p&gt;+1&lt;/p&gt;</comment>
                            <comment id="277962" author="ifor" created="Thu, 28 Feb 2013 10:53:38 +0000"  >&lt;p&gt;+1 Getting the name right first time - isn&apos;t Agile&lt;/p&gt;</comment>
                            <comment id="179991" author="maciej.gajewski" created="Mon, 29 Oct 2012 09:30:09 +0000"  >&lt;p&gt;+1&lt;/p&gt;</comment>
                            <comment id="167536" author="jakiao" created="Mon, 24 Sep 2012 21:30:59 +0000"  >&lt;p&gt;+1 for this feature as well.  It&apos;s confusing to think it isn&apos;t already supported and is only a minor priority issue.&lt;/p&gt;</comment>
                            <comment id="149854" author="reda" created="Thu, 2 Aug 2012 14:20:45 +0000"  >&lt;p&gt;this a medium priority requirement, i think it&apos;s an essential feature.&lt;/p&gt;</comment>
                            <comment id="144051" author="pumpkin" created="Tue, 17 Jul 2012 15:49:30 +0000"  >&lt;p&gt;Another +1 for this new feature.&lt;br/&gt;
cloning the database every time we need to rename it is becoming a hassle.&lt;/p&gt;</comment>
                            <comment id="141799" author="gavinaiken" created="Wed, 11 Jul 2012 12:57:46 +0000"  >&lt;p&gt;This would definitely give some flexibility in moving data around quickly as systems grow. Example use case - in EC2 (and many raid systems) you can take a quick snapshot of a running mongo db and create a new disk vol on another server almost immediately. So if you want to move a big collection onto its own server with almost no downtime, you do the snapshot procedure, drop the collection from the original server/db and drop all the other unwanted collections from the copied snapshotted db on the new server. It would be good to then rename the db on the new server as a final step to avoid confusion, and to avoid having to copy the data out and in again which could take hours. Otherwise you have the same db name on 2 different servers but with different collections in each.&lt;/p&gt;</comment>
                            <comment id="81937" author="christian.tonhaeuser@navteq.com" created="Tue, 24 Jan 2012 14:05:21 +0000"  >&lt;p&gt;+1 for being able to rename databases.&lt;br/&gt;
Database names play a huge role in our application, so being able to rename them easily would be a killer feature.&lt;br/&gt;
Also, I don&apos;t really understand why a seemingly simple feature like this hasn&apos;t been implemented long ago, after all, this ticket is almost two years old now.&lt;/p&gt;</comment>
                            <comment id="67768" author="bjornharvold" created="Sun, 20 Nov 2011 08:37:53 +0000"  >&lt;p&gt;I&apos;d like to see this feature supported as well.&lt;/p&gt;</comment>
                            <comment id="56767" author="m.korbakov@nimble.com" created="Mon, 26 Sep 2011 22:08:09 +0000"  >&lt;p&gt;Any plans for including it into coming releases? Having it solved would help us migrating to sharded MongoDB cluster.&lt;/p&gt;</comment>
                            <comment id="50510" author="crudson" created="Wed, 24 Aug 2011 17:17:12 +0000"  >&lt;p&gt;We get replacement datasets periodically and it would be helpful to just rename a db to some archived name, and keep using the original db name (without the fuss of copy/export/import and configuration management of db names).&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                                                <inwardlinks description="is depended on by">
                                                        </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                                        </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="959079">TOOLS-2387</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="920016">DOCS-13024</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>45.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_13552" key="com.go2group.jira.plugin.crm:crm_generic_field">
                        <customfieldname>Case</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[[500A000000UaSEwIAN, 500A000000bBhlIIAS, 5002K00000e7EIeQAM, 5002K00000e9jhyQAA, 5002K00000eikcfQAA, 5002K00000huZsWQAU, 5002K00000hueVmQAI, 5002K00000kFW3ZQAW, 5002K00000nDqe2QAC, 5002K00000od8aLQAQ, 5002K00000odmJDQAY, 5002K00000pG7vZQAS, 5002K00000s1lnRQAQ, 5002K00000zAw0tQAC, 5006R00001pk2A8QAI]]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Wed, 24 Aug 2011 17:17:12 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        1 year, 39 weeks, 1 day ago
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18254" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Dependencies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[]]></customfieldvalue>


                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10057" key="com.atlassian.jira.toolkit:lastusercommented">
                        <customfieldname>Last comment by Customer</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>true</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10056" key="com.atlassian.jira.toolkit:lastupdaterorcommenter">
                        <customfieldname>Last commenter</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>luke.bonanomi@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            1 year, 39 weeks, 1 day ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10000" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Old_Backport</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10000"><![CDATA[No]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>zugwalt</customfieldvalue>
            <customfieldvalue>airs0urce</customfieldvalue>
            <customfieldvalue>alecyu</customfieldvalue>
            <customfieldvalue>mobafill</customfieldvalue>
            <customfieldvalue>amey.potnis@gmail.com</customfieldvalue>
            <customfieldvalue>farquaad</customfieldvalue>
            <customfieldvalue>andrey.hohutkin@gmail.com</customfieldvalue>
            <customfieldvalue>anupk</customfieldvalue>
            <customfieldvalue>asya.kamsky@mongodb.com</customfieldvalue>
            <customfieldvalue>bjornharvold</customfieldvalue>
            <customfieldvalue>bkonash@squarespace.com</customfieldvalue>
            <customfieldvalue>brian.lane@mongodb.com</customfieldvalue>
            <customfieldvalue>christian.tonhaeuser@navteq.com</customfieldvalue>
            <customfieldvalue>dandv</customfieldvalue>
            <customfieldvalue>alice@gothcandy.com</customfieldvalue>
            <customfieldvalue>djvw@redscreen.co.za</customfieldvalue>
            <customfieldvalue>crudson</customfieldvalue>
            <customfieldvalue>ejones</customfieldvalue>
            <customfieldvalue>gavinaiken</customfieldvalue>
            <customfieldvalue>jakiao</customfieldvalue>
            <customfieldvalue>guillermo85</customfieldvalue>
            <customfieldvalue>ifor</customfieldvalue>
            <customfieldvalue>diversario</customfieldvalue>
            <customfieldvalue>brezniczky@gmail.com</customfieldvalue>
            <customfieldvalue>jlyonsmith</customfieldvalue>
            <customfieldvalue>pumpkin</customfieldvalue>
            <customfieldvalue>justin@idle-games.com</customfieldvalue>
            <customfieldvalue>kmehta</customfieldvalue>
            <customfieldvalue>legel</customfieldvalue>
            <customfieldvalue>maciej.gajewski</customfieldvalue>
            <customfieldvalue>m.korbakov@nimble.com</customfieldvalue>
            <customfieldvalue>nwerneck</customfieldvalue>
            <customfieldvalue>reda</customfieldvalue>
            <customfieldvalue>rgpublic</customfieldvalue>
            <customfieldvalue>rob_colella@volusion.com</customfieldvalue>
            <customfieldvalue>sherryummen</customfieldvalue>
            <customfieldvalue>steven.vannelli@mongodb.com</customfieldvalue>
            <customfieldvalue>sunnybg</customfieldvalue>
            <customfieldvalue>hu.sesselmann@dsfishlabs.com</customfieldvalue>
            <customfieldvalue>hedefalk</customfieldvalue>
            <customfieldvalue>kreig</customfieldvalue>
            <customfieldvalue>ygbr@mac.com</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrpr4v:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hr77f3:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>6061</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_23361" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Requested By</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_22870" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Triagers</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11861" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>User Summary</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="11858"><![CDATA[Completed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_14350" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>serverRank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrizsn:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>