[MGNLEESOLR-85] Integer.MAX_VALUE is too big for maxResultsPerPage default value. Created: 05/Oct/15  Updated: 15/Apr/16  Resolved: 09/Oct/15

Status: Closed
Project: Solr Search Provider
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0

Type: Bug Priority: Neutral
Reporter: Evzen Fochr Assignee: Evzen Fochr
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 0.5h
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLEESOLR-67 Support Solr 5 Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Kromeriz 14
Story Points: 1

 Description   

We use Integer.MAX_VALUE in AbstractSearchResultModel as maxResultsPerPage default value. Solr5 cannot work with such big number for rows (overflow in solr).
We should use about 1 mil or so as default value.



 Comments   
Comment by Milan Divilek [ 09/Oct/15 ]

Reopen: MAX_RESULTS_PER_PAGE_DEFAULT_VALUE make it private and I would set it to 10 000 by default same as in STKPager.

Generated at Mon Feb 12 10:59:57 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.