Hello all,
I have just finished to book Solr 1.4 Enterprise Search Server. I now
understand most of the basics of Solr and also how we can scale the solution.
Our goal is to have a centralized search service for a multitude of apps.
Our first application which we want to index, is a system in
Your users will have to accept some latency between changed permissions and
those permissions being reflected in the results. The length of that latency is
determined by two things:
1 the interval between when you send the change to Solr (i.e.
re-index the doc)
and issue a commit
AND
2 the time it
You could commit on a time schedule. Like every 5 mins. If there is nothing to
commit it doesn't do anything anyway.
Bill Bell
Sent from mobile
On Feb 11, 2011, at 8:22 AM, Greg Georges greg.geor...@biztree.com wrote:
Hello all,
I have just finished to book Solr 1.4 Enterprise Search
On Fri, Feb 11, 2011 at 10:47 AM, Bill Bell billnb...@gmail.com wrote:
You could commit on a time schedule. Like every 5 mins. If there is nothing
to commit it doesn't do anything anyway.
It does do something! A new searcher is opened and caches are invalidated, etc.
I'd recommend normally
Thanks. If you do 2 commits should it do anything? Are people using it to clear
caches?
Bill Bell
Sent from mobile
On Feb 11, 2011, at 9:55 AM, Yonik Seeley yo...@lucidimagination.com wrote:
On Fri, Feb 11, 2011 at 10:47 AM, Bill Bell billnb...@gmail.com wrote:
You could commit on a time
