Feature #3898
closed
Pagination should be turned off by default in --csv mode
Description
The pagination should be turned off by default when using csv output adapter. Csv is intended to be used primarily for machine processing so there's not much use in pagination. This behaviour can be overridden by passing --per-page implicitly.
Depends on: http://projects.theforeman.org/issues/3652
Updated by Dominic Cleal almost 10 years ago
- Blocked by Feature #3652: Add explicit way for API consumers to specifiy all pages in an index request added
Updated by Dominic Cleal over 9 years ago
- Related to Bug #5073: [RFE] Ability to disable pagination added
Updated by Dominic Cleal almost 9 years ago
- Has duplicate Bug #8568: Hammer host list does not paginate correctly when interactive is set to "no" added
Updated by Tom Caspy almost 9 years ago
- Status changed from New to Ready For Testing
- Assignee set to Tom Caspy
- Pull request https://github.com/theforeman/hammer-cli-foreman/pull/160 added
Updated by Anonymous almost 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset hammer-cli-foreman|ae520bbb7bccbc38ba55938fb5f05c3cb5a71298.
Updated by Tomáš Strachota almost 9 years ago
- Status changed from Closed to New
- % Done changed from 100 to 0
I'm reopening the issue since the PR actually fixed something different. It only turns off interactivity but data returned from server remain paginated.
I'm sorry if the issue description wasn't clear enough. Please contact me if you need more details.
Updated by Tom Caspy almost 9 years ago
this is by design. the data can't return without pagination (imagine a query returning 100K results, which is definitely possible)
the idea is that the machine reading the data will go through the pagination programatically.
i.e. this pseudo code:
current_results = get first page
all results += current_results
while current_results.size < per_page
current_results = get next page
all_results += current_results
end
Updated by Ohad Levy almost 9 years ago
Tom Caspy wrote:
this is by design. the data can't return without pagination (imagine a query returning 100K results, which is definitely possible)
I would assume that we can increase the default page size when we are in batch mode, so instead of 20 results, you can query for 500 or 1000 at a time?
Updated by Tom Caspy almost 9 years ago
yes. there are page and per_page options.
Updated by Dominic Cleal over 8 years ago
- Has duplicate Bug #10313: hammer truncates output when interactive=false added
Updated by Tomáš Strachota over 8 years ago
- Related to Bug #10534: hammer pagination output should be disabled by default or respect terminal size added
Updated by Dominic Cleal over 8 years ago
- Status changed from New to Duplicate
- Assignee deleted (
Tom Caspy)
Agreed.