Yonik Seeley wrote: > On 10/23/06, Paul Waite <[EMAIL PROTECTED]> wrote: > > However if I understand the above properly, we should implement a > > strategy which at least limits the commit frequency, to prevent the > > scenario you describe in the last para above.
> Right. If a new news item comes in, you could do a commit immediately > and then ensure that another commit is not done within "x" amount of > time. > Some ideas on features I've never had the chance to implement are > minimumCommitFrequency (like described above) and > auto commit (let solr decide when to commit... after x docs or y > seconds w/o a commit). > I'd accept patches that baked any of that stuff into Solr :-) http://wiki.apache.org/solr/SolrConfigXml In the UpdateHandler section I see: <updateHandler class="solar.DirectUpdateHandler2"> <!-- autocommit pending docs if certain criteria are met --> <autocommit> <!-- NOTE: autocommit not implemented yet --> <maxDocs>10000</maxDocs> <maxSec>3600</maxSec> </autocommit> <!-- represents a lower bound on the frequency that commits may occur (in seconds). NOTE: not yet implemented --> <commitIntervalLowerBound>0</commitIntervalLowerBound> So the hard part is already done - the parameters are named! ;-) Cheers, Paul.
