Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-30123

clarify seekExact behaviors

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • 3.4.6
    • Storage
    • None
    • Storage Execution
    • Execution Team 2020-01-13, Execution Team 2020-01-27, Execution Team 2020-02-10, Execution Team 2020-02-24, Execution Team 2020-04-20, Execution Team 2020-06-29

    Description

      Currently, seekExact on a record store in WiredTiger has the following behavior:
      After the first call to seekExact(), a call to next() will repeat the same answer (either eof or the record that was seek'd).
      However, I found code (currently unused) that seems to assume that calling next() after seekExact() will have normal cursor semantics and actually return the next record after the one that was seek'd. I could find no comments or tests that lock in one behavior or the other. We should make it clear what the behavior should be for all storage engines.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: