If I understand correctly, you SORT on login_time desc.
Perhaps your biggest problem is that for each user logging in, they jump to
page 1, so this issue is very visible.
A simple way to fix this is to add a filter when you page, e.g.
fq=login_time:[* TO ], effectively freezing the time
window y
Thanks for the replies. I did look at caching but our commit time time is 90
seconds. It's definitely possible for someone to make a search, change the
page, and have wonky results. How about getting it to autowarm the x most
recent searches in the queryResultCache and that can hopefully reduce
om: lee carroll [mailto:lee.a.carr...@googlemail.com]
Sent: Thursday, August 25, 2011 6:33 AM
To: solr-user@lucene.apache.org
Subject: Re: Best way to anchor solr searches?
I don't think solr conforms to ACID type behaviours for its queries.
This is not to say your use-case is not important
just that its not S
I don't think solr conforms to ACID type behaviours for its queries.
This is not to say your use-case is not important
just that its not SOLR's focus. I think its a interesting question but
the solution is probably going to involve rolling your own.
Something like returning 1 user docs and cac
