Uploaded image for project: 'MongoDB Shell'
  1. MongoDB Shell
  2. MONGOSH-361

Batch size & Type "it" for more

    • Type: Icon: Story Story
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 0.7.7
    • Affects Version/s: None
    • Component/s: None
    • 5
    • Iteration Star Apple
    • Needed
    • Hide

      DBQuery.shellBatchSize is deprecated and not used for this, unlike the issue description states.

      The documentation for the old shell states that cursor.batchSize() does not control the output display size in the shell. That is no longer true: It does control the output display size (in addition to also setting the driver batchSize), and it is the only thing that does that.

      Show
      DBQuery.shellBatchSize is deprecated and not used for this, unlike the issue description states. The documentation for the old shell states that cursor.batchSize() does not control the output display size in the shell. That is no longer true: It does control the output display size (in addition to also setting the driver batchSize), and it is the only thing that does that.

      User Story

      As a user,
      I want to control the batch size when I issue my queries and aggregations
      So that I can customize it to my needs and my screen size

      Acceptance criteria

      • It's possible to set DBQuery.shellBatchSize to control the batch size for queries and aggregations (default is 20)
      • When a query or an aggregation returns more than DBQuery.shellBatchSize results, results are paginated and each page includes at most DBQuery.shellBatchSize results
      • When there are more pages of results to see, the shell prints Type "it" for more
      • It should not be possible to delete DBQuery.shellBatchSize

            Assignee:
            anna.henningsen@mongodb.com Anna Henningsen
            Reporter:
            massimiliano.marcon@mongodb.com Massimiliano Marcon
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: