Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.4.0-rc6
Affects Version/s: 4.4.0-rc4
Component/s: Index Maintenance, Querying, Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v4.4
Sprint:
Query 2020-05-18
Linked BF Score:
38
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

collMod creates oplog entries, even when it does nothing. In FCV 4.2, it can create this oplog entry:

  {dbName: 'db10',commandObj: {collMod: 'coll12',index: {name: 'idx_f',hidden: false}}},

It's not rejected since it's "hidden: false", but also 4.2 is unhappy due to this logic that expects an "expireAfterSeconds" field.

is caused by

SERVER-9306 Ability to temporarily forbid query optimizer from using index ("invisible index")

Closed

related to

SERVER-61980 collMod does not consider unique option in no-op hidden parameter request processing

Closed

SERVER-62000 Do not generate "unique" field in oplog if collMod "unique" parameter is a no-op

Closed

SERVER-48397 Make collMod no-op behaviour consistent

Backlog

Assignee:: Ruoxin Xu
Reporter:: Judah Schvimer
Participants:: Githook User, Judah Schvimer, Ruoxin Xu
Votes:: 0 Vote for this issue
Watchers:: 9 Start watching this issue

Created:: May 08 2020 04:12:59 PM UTC
Updated:: Oct 29 2023 10:08:30 PM UTC
Resolved:: May 14 2020 11:14:34 AM UTC