Details
-
Improvement
-
Resolution: Fixed
-
Minor
-
2.5.0
-
Security Level: Public
Description
Currently, for buckets where rate of document changes is low, stale query is very impractical. Frequency of view updates is essentially controlled by updateMinChanges. When documents are changed at a very low rate, indices may not be rebuilt in quite some time. It will be very useful, if we could also have a timeout value for an index build. If the timeout expires and at least one document has changed then the index should be rebuilt. This way, the index will be eventually consistent within a guaranteed time period.
Example use cases will be browse heavy sites, like blogs and startups where initially user activity is minimal. I find stale queries not a good fit for this situation. And stale=false is what I choose to do. Once the site gets busy, I will need to go through code and enable stale query. A timeout based approach will, I think, be very convenient.