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

Change WT_NOT_FOUND to WT_NOTFOUND in comment in hs_rec.c

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Minor - P4 Minor - P4
    • WT11.1.0, 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None

      Fix this comment in hs_rec.c:

          /*
           * Look ahead for any higher timestamps. If we find updates, we should remove them and reinsert
           * them at the current timestamp. If there were no keys equal to or less than our target key, we
           * would have received WT_NOT_FOUND. In that case we need to search again with a higher
           * timestamp.
           */

      WT_NOT_FOUND should read WT_NOTFOUND.

            Assignee:
            keith.smith@mongodb.com Keith Smith
            Reporter:
            keith.smith@mongodb.com Keith Smith
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: