[SERVER-43177] Add a query flag for oplog reads to ignore oplog visibility rules Created: 05/Sep/19 Updated: 07/Oct/19 Resolved: 07/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Charlie Swanson |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Query 2019-10-07, Query 2019-10-21 |
| Participants: |
| Description |
|
Add a query flag that tells the query system to simply ignore oplog visibility even for forward cursors, for internal use. This is useful especially for TransactionHistoryIterator where we want to be able to see everything immediately. |
| Comments |
| Comment by Eric Milkie [ 07/Oct/19 ] |
|
Agreed, this flag isn't needed at this time. |
| Comment by Lingzhi Deng [ 03/Oct/19 ] |
|
I think we can safely close this ticket as "Won't fix". I don't think there is any issue in production code and |
| Comment by David Storch [ 09/Sep/19 ] |
|
Putting into Investigating. The query team plans to talk with the repl team in order to understand why this flag is needed. |