Summary
What is the problem or use case, what are we trying to achieve?
To aggregate the record count for a table
Motivation
- Does this affect any team outside of WT?
(Are they blocked? Are they waiting for an answer?)
Not immediately, this is a new feature.
- How likely is it that this use case or problem will occur?
(Main path? Edge case? Frequency of the issue?)
This is part of a new feature
- If the problem does occur, what are the consequences and how severe are they?
(A minor annoyance at a log message? Performance concern? Outage/unavailability? Test Failure?)
NA
- Is this issue urgent?
(Does this ticket have a required timeline? What is it?)
No.
Acceptance Criteria (Definition of Done)
(When will this ticket be considered done? What is the acceptance criteria for this ticket to be closed?)
- Testing
(What all testing needs to be done as part of this ticket? Unit? Functional? Performance?Testing at MongoDB side?)
- Documentation update
(Does this ticket require a change in the architecture guide? If yes, please create a corresponding doc ticket.)
[Optional] Suggested Solution
(Is there any suggested solution to handle this issue? Is it related to any existing WT ticket? Is it related to any previous issue fixed? If yes, link the WT ticket number using related to, depends on, dependent on by links)
The record count field to be part of :
Leaf page, intermediate page, root page and meta data entry.
- is depended on by
-
WT-10198 Implement the drop operation of the run phase
- Closed