You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Mike Klaas (JIRA)" <ji...@apache.org> on 2007/02/01 20:44:05 UTC

[jira] Commented: (SOLR-126) Auto-commit documents after time interval

    [ https://issues.apache.org/jira/browse/SOLR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469559 ] 

Mike Klaas commented on SOLR-126:
---------------------------------

Committed in r502328.  Thanks!

Ryan, the last comment of mine was about the units of time that <maxTime> was specified in--the old version had the time specified in seconds and the parameter name was <maxSec>.  I committed it the way it stands in the patch; if anyone has a strong opinion, this can be changed before being closed.

> Auto-commit documents after time interval
> -----------------------------------------
>
>                 Key: SOLR-126
>                 URL: https://issues.apache.org/jira/browse/SOLR-126
>             Project: Solr
>          Issue Type: Improvement
>          Components: update
>            Reporter: Ryan McKinley
>            Priority: Minor
>         Attachments: AutoCommit.patch, AutocommitingUpdateRequestHandler.patch
>
>
> If an index is getting updated from multiple sources and needs to add documents reasonably quickly, there should be a good solr side mechanism to help prevent the client from spawning multiple overlapping <commit/> commands.
> My specific use case is sending each document to solr every time hibernate saves an object (see SOLR-20).  This happens from multiple machines simultaneously.  I'd like solr to make sure the documents are committed within a second.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.