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

Complex tables unintentionally clears bounds with cursor remove operation

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • 5

      In the case of a complex table and when the user performs a remove operation, is it possible that we call reset() after the remove operation was completed.

          F_CLR(primary, WT_CURSTD_KEY_SET | WT_CURSTD_VALUE_SET);
          if (positioned)
              F_SET(primary, WT_CURSTD_KEY_INT);
          else
              APPLY_CG(ctable, reset);
      

      The bounds unintentionally gets cleared here, which is not expected behaviour. This ticket needs to investigate and fix this problem.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            jie.chen@mongodb.com Jie Chen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: