Consider not skipping first document when specifying minKey in dbCheck

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, when running a data consistency or missing keys check with a minKey specified, we will skip the first document that refers to the minKey. This may be confusing for users, so we should consider not skipping that document.

              Assignee:
              Unassigned
              Reporter:
              Xuerui Fa
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: