Question

最近,我开始使用库什从事一米工作。

I database with 7907 documents, and wanted to rename the database. I poked around for a bit, but couldn t figure out how to rename it, so I figured I would just replicate it to a local database of the name I wanted.

我第一次尝试了复制失败,我认为这一错误是空洞。我再一次尝试,而且工作非常快,令人不安。

在复制后,Im显示新数据库有正确的记录,但数据库规模约为原始数据的三分之一。

还有一点奇怪的是,如果我重新找回了葬礼,原来的面积在94.6至95.5平方米之间浮动。

下面我要谈谈几个问题:

第2数据库是否储存了第1条的参考资料? 如果是的话,我是否可以删除第一起,而不造成伤害?
为什么规模如此不同? 原始建筑指数是否最终会变?
Why is the size fluctuating?

<><>>:>

可能有助于:

This is on a cloudant couchdb install
I checked the first and last record of the new db, and they match, so I don t believe futon is underreporting.

Answer 1

复制到一个新的数据库类似于契约。两者都涉及某些副作用(明显和有意地分别涉及),以减少新的<代码>.co文档的规模。

The b-tree indexes get balanced
Data from old document revisions is discarded.
Metadata from previous updates to the DB is discarded.

复制品储存到/从检查站,这样,如果你从同一来源复制到同一地点(即重新复制时间缩短),就将搬离。

答复:

Replication does not create a reference to another database. You can delete the first without causing harm.
Replicating (and compacting) generally reduces disk usage. If you have any views in any design documents, those will re-build when you first query them. View indexes use their own .view file which also consumes space.
I am not sure why the size is fluctuating. Browser and proxy caches are the bane of CouchDB (and web) development. But perhaps it is also a result of internal Cloudant behavior (for example, different nodes in the cluster reporting slightly different sizes).

友情链接