[
https://issues.apache.org/jira/browse/SOLR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468497
]
Yonik Seeley commented on SOLR-126:
-----------------------------------
Thanks for tackling this Ryan, this is much needed functionality (planned since
inception but never coded!)
This should definitely go into the existing committracker/updatehandler.
Timer/TimerTask for the timers? Haven't used them myself... are they
appropriate?
Some future issues (i.e. a different JIRA issue)... one setting may make
perfect sense when doing incremental updates, to enforce a minimum "freshness"
and take the burden of commit off of the clients. When building an index from
scratch, you want to do it as quickly as possible, and not do commits all the
time (or even expose a partial index to searches).
Perhaps something like &autocommit=false in the update params?
It might even be nice to be able to change the mergeFactor for a complete index
build vs incremental updates.
> 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: 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.
