filemd5 command hides execution error in some cases

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.1.7
    • Component/s: GridFS
    • None
    • Query
    • ALL
    • Hide

      1. Import a large file with mongofiles.
      2. Drop the

      { files_id: 1, n: 1 }

      index.
      3. Create a

      { files_id: 1 }

      index. This will make the planner select this and not fail because table scan is not allowed in filemd5.
      4. Call filemd5 on the file.

      Show
      1. Import a large file with mongofiles. 2. Drop the { files_id: 1, n: 1 } index. 3. Create a { files_id: 1 } index. This will make the planner select this and not fail because table scan is not allowed in filemd5. 4. Call filemd5 on the file.
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When filemd5 command exceeds the sort memory limit, it does not report the error but instead return a result as if the file was empty.

      A modified version of the existing gridfs.js is attached.

              Assignee:
              Backlog - Query Team (Inactive)
              Reporter:
              Randolph Tan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: