Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-5722

Support a 'sort' field in ops array for JS Benchmarking Harness

    Details

      Issue Links

        Activity

        Hide
        pasette Dan Pasette added a comment - - edited

        You can add a sort by adding an orderBy clause into the query document.

        { op: "find",
                 query: { $query: {x: { $gte : 0 }}, $orderby : {"x" : 1} }
        }
        

        Show
        pasette Dan Pasette added a comment - - edited You can add a sort by adding an orderBy clause into the query document. { op: "find", query: { $query: {x: { $gte : 0 }}, $orderby : {"x" : 1} } }
        Hide
        david.storch David Storch added a comment - - edited

        Despite the workaround above for legacy OP_QUERY find, my reading of the shell's implementation of benchRun in the master branch suggests that neither a "sort" nor an "orderby" field is supported when find command is enabled via the readCmd option. It would be useful to support this option in a general way for both find command and legacy OP_QUERY, so I am re-opening this ticket for consideration by the performance infrastructure team.

        Show
        david.storch David Storch added a comment - - edited Despite the workaround above for legacy OP_QUERY find, my reading of the shell's implementation of benchRun in the master branch suggests that neither a "sort" nor an "orderby" field is supported when find command is enabled via the readCmd option. It would be useful to support this option in a general way for both find command and legacy OP_QUERY, so I am re-opening this ticket for consideration by the performance infrastructure team.
        Hide
        kyle.suarez Kyle Suarez added a comment -

        Having this would be especially helpful for the views project. They require --readCmd true to work properly, so we cannot apply a views passthrough to existing query tests that rely on the $query example that Dan mentioned, since that's not supported in read commands.

        Show
        kyle.suarez Kyle Suarez added a comment - Having this would be especially helpful for the views project. They require --readCmd true to work properly, so we cannot apply a views passthrough to existing query tests that rely on the $query example that Dan mentioned, since that's not supported in read commands.
        Hide
        david.daly David Daly added a comment -

        David Storch Kyle Suarez Would the addition fit here (that's FindOne. Also for find) for the readCmd path, and create something similar to our current work around for the non readCmd path?

        Show
        david.daly David Daly added a comment - David Storch Kyle Suarez Would the addition fit here (that's FindOne. Also for find) for the readCmd path, and create something similar to our current work around for the non readCmd path?
        Hide
        david.storch David Storch added a comment -

        David Daly, yep, that sounds right to me.

        Show
        david.storch David Storch added a comment - David Daly , yep, that sounds right to me.

          People

          • Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

            • Created:
              Updated:
              Days since reply:
              2 weeks, 2 days ago
              Date of 1st Reply: