Cursor seekExact should not use WT_CURSOR:search_near to avoid unintentional prepare conflicts

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication, Storage
    • ALL
    • Storage NYC 2019-04-08, Storage NYC 2019-05-06, Storage NYC 2019-05-20
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      As described in SERVER-40167, seeking using search_near can cause operations to encounter unintended prepare conflicts when the queried key is not found.

            Assignee:
            Louis Williams
            Reporter:
            Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated:
              Resolved: