[DOCS-13452] 4.2 only: remove index metadata.infoObj fields from examples. Created: 26/Feb/20  Updated: 13/Nov/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.1.12, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Minor - P4
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-41073 Writing index metainfo into WT's app_... Closed
Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

Description

Downstream Change Summary

In 4.2, just need to update example outputs that show this field in collStats pages.
4.4 is already being done when updating output for another ticket.

Description of Linked Ticket

Since as far as I care to look back, mongodb has passed index "info objects" to the WT table's app_metadata. The index data is converted to a json string representation which contains the collection name.

When this string is malformed and WT hits a parsing error, it's typically discovered via the primary and results in a uassert:

test> db.createCollection("\x7F")
{
	"ok" : 0,
	"errmsg" : "22: Invalid argument",
	"code" : 2,
	"codeName" : "BadValue"
}

However an existing collection can be renamed without renaming the ns field on an index entry:

test> db.foo.renameCollection("\x7F")
{ "ok" : 1 }
test> db["\x7F"].find()
{ "_id" : ObjectId("5cd472baae8328407ec23421") }

With the new unique index format, indexes can have their metadata re-written to note the format the index is currently in. This can happen on an empty collMod command. There are cases where a primary will replicate this collMod without having hit the parsing error itself. A secondary processing this oplog entry will crash.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Generated at Thu Feb 08 08:07:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.