mongoebench-compatible JSON config files attempt to read from views without using "find" command

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • v4.0
    • TIG 2018-09-10, TIG 2018-09-24
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The benchrun.py script defaults to --readCmd=false as seen in the mongoebench-compatible JSON config file with "readCmd" : false.

      benchrun_embedded/testcases/queries_identity_view_int_id_find_one.json
      Unable to find source-code formatter for language: text. Available languages are: actionscript, ada, applescript, bash, c, c#, c++, cpp, css, erlang, go, groovy, haskell, html, java, javascript, js, json, lua, none, nyan, objc, perl, php, python, r, rainbow, ruby, scala, sh, sql, swift, visualbasic, xml, yaml
      ...
"writeConcern" : { "j" : false },
"writeCmd" : true,
"readCmd" : false } ] }

      This causes DBClientConnection::findOne() to be called rather than DBClientConnection::runCommand() being called via runQueryWithReadCommands(). Legacy OP_QUERY reads do not support views - only the "find" command does. Changing the mongoebench-compatible JSON config files to be generated with --readCmd=true would address this issue.

            Assignee:
            Max Hirschhorn
            Reporter:
            Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: