Complex tables unintentionally clears bounds with cursor remove operation

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • 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:
              [DO NOT USE] Backlog - Storage Engines Team
              Reporter:
              Jie Chen
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: