Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-10815

Avoid RTS bypassing history cursor interface

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: RTS
    • 8
    • StorEng - Defined Pipeline

      (Created as a result of WT-10270)

      The RTS subsystem contains two direct calls for history store cursors:

      • wt_curhs_search_near_after
      • wt_curhs_search_near_before

      Most cursor API calls go via a function pointer from a WT_CURSOR structure, these two bypass that because they aren't part of the standard cursor interface. We should introduce a new flag to cursors, that allows applications (in this case WiredTiger itself) to control search_near behaviour.

      Some caution should be exercised here - this would be an addition to external-facing APIs, so extra thought is warranted about having a clean interface that could also be useful to non-WiredTiger users. (The MongoDB oplog is one such application, where it would be useful to give hints about the direction of a search_near.)

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            will.korteland@mongodb.com Will Korteland
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: