e.g. There are 4,000 solr documents that were found for a particular word search. My app has entitlement rules applied to those 4,000 documents and it's quite possible that user is only eligible to view 3,000 results out of 4K. This is achieved through post filtering application logic.
My question related to solr pagination is : In order to paint "Next" links app would have to know total number of records that user is eligible for read. getNumFound() will tell me that there are total 4K records that Solr returned. If there wasn't any entitlement rules then it could have been easier to determine how many "Next" links to paint and when user clicks on "Next" pass in "start" position appropriately in solr query. Since I have to apply post filter as and when results are fetched from Solr is there a better way to achieve this? e.g. Because of post filtering I wouldn't know whether to paint "Next" link until results for "next" links are pre-fetched and filtered. Pre-fetching won't work as that would kill the performance and have no meaning of Solr pagination. Any better suggestion? Thanks, -- View this message in context: http://lucene.472066.n3.nabble.com/Smart-Pagination-queries-tp2652273p2652273.html Sent from the Solr - User mailing list archive at Nabble.com.
