[MGNLEESOLR-76] Do not handle differently with search results in different providers/models Created: 18/Aug/15  Updated: 15/Apr/16  Resolved: 18/Aug/15

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

Type: Improvement Priority: Major
Reporter: Milan Divilek Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLEESOLR-69 Stop using non serialisable objects i... Closed
caused by MGNLEESOLR-66 Free the solr-search-provider modules... 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)
Sprint: Sprint 6 (Kromeriz)
Story Points: 2

 Description   

Handling with the faceted search results was changed in MGNLEESOLR-69.
Search results are not persisted in FacetedSolrSearchProvider (is not @SessionScoped anymore) and result are not filled into pager directly.
Instead of it we introduce new FacetedSolrSearchResults object where the results are persisted.
FacetedSolrSearchProvider uses FacetedSolrSearchResults and FacetedSolrPager(which just delegates to FacetedSolrSearchResults#getCount and FacetedSolrSearchResults.getSearchResultItems methods), but SimilarSearchProvider uses just SolrPager where you have to set the results. So we end up with two SolrPager implementations and we are handling with results differently in different providers.


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