jstests/noPassthrough/atomic_rename_collection.js


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33

(function() {
    // SERVER-28285 When renameCollection drops the target collection, it should just generate
    // a single oplog entry, so we cannot end up in a state where the drop has succeeded, but
    // the rename didn't.
    let rs = new ReplSetTest({nodes: 1});
    rs.startSet();
    rs.initiate();

    let prim = rs.getPrimary();
    let first = prim.getDB("first");
    let second = prim.getDB("second");
    let local = prim.getDB("local");

    // Test both for rename within a database as across databases.
    [{source: first.x, target: first.y}, {source: first.x, target: second.x}].forEach((test) => {
        test.source.drop();
        assert.writeOK(test.source.insert({}));
        assert.writeOK(test.target.insert({}));

        let ts = local.oplog.rs.find().sort({$natural: -1}).limit(1).next().ts;
        let cmd = {
            renameCollection: test.source.toString(),
            to: test.target.toString(),
            dropTarget: true
        };
        assert.commandWorked(local.adminCommand(cmd), tojson(cmd));
        ops = local.oplog.rs.find({ts: {$gt: ts}}).sort({$natural: 1}).toArray();
        assert.eq(
            ops.length,
            1,
            "renameCollection was supposed to only generate a single oplog entry: " + tojson(ops));
    });
})();