Replace top-level zero timestamp with current timestamp for consistency and implement bypassEmptyTsReplacement parameter

[AlekSi]

Describe the bug

Inserting a zero timestamp value (Timestamp(0, 0)) as a top-level document field should insert a non-zero timestamp based on the current time, like in MongoDB.

Reproduction Steps

const coll = db.test;

coll.drop();

const doc = {
  _id: "id",
  v: Timestamp(0, 0),
  d: {
    dv: Timestamp(0, 0),
  }
}

coll.insert(doc);

const actual = coll.find({}).toArray()[0];
assert.eq("id", actual._id);

const now = Date.now() / 1000;

assert.neq(Timestamp(0, 0), actual.v);
assert.neq(0, actual.v.i);
assert.between(now - 5, actual.v.t, now + 5);

assert.eq(Timestamp(0, 0), actual.d.dv);
assert.eq(0, actual.d.dv.i);

See FerretDB/FerretDB#5200 and FerretDB/FerretDB#5199.

Expected behavior

Test passes.

Actual behavior

DocumentDB inserts both timestamps as Timestamp(0, 0). Test fails.

[lichoil]

we've ignored this parameter in new sync. @AlekSi

[AlekSi]

There is no parameter in this issue

[lichoil]

we've repro this issue in mongo8.0 driver client. so we change our backend to ignore this param. this will unblock customers using mnongimport/mongoexport/mongodump/mongorestore new version.

[lichoil]

default setting in mongogimport/mongoexport/mongodump/mongorestore tool for this parameter is True, which align with documentDB behavior, so we can safely ignore this param.

[AlekSi]

Again, there is no parameter in this issue, as it stands now. If you want to repurpose it for something else, please update the title and description.

[AlekSi]

I think that issue could be closed as not planned for the time being.