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

Fix leaf-page only search and search-near operations

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.1, WT3.2.2, 4.2.2
    • Component/s: None
    • Labels:
      None
    • Story Points:
      5
    • Sprint:
      Storage Engines 2019-10-07

      Description

      WT-3769 broke leaf-page only searches.

      The WT_CURSOR.search and WT_CURSOR.search_near operations are supposed to search any pinned Btree leaf page (that is, any page pinned as a result of a previous operation), assuming locality of reference, that a search is likely to hit on the currently pinned page. Commit 00e1b59 broke this by checking if the current key was internal (referencing an on-page key) or external (referencing a key set by the application using WT_CURSOR.set_key). That test was correct for non-search operations (for example, WT_CURSOR.update, but not for search operations).

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              keith.bostic Keith Bostic
              Reporter:
              keith.bostic Keith Bostic
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: