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 "Ryan McKinley (JIRA)" <ji...@apache.org> on 2008/12/18 14:25:44 UTC
[jira] Updated: (SOLR-793) set a commit time bounds in the
command
[ https://issues.apache.org/jira/browse/SOLR-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan McKinley updated SOLR-793:
-------------------------------
Description:
Currently there are two options for how to handle commiting documents:
1. the client explicitly starts the commit via <commit/>
2. set an auto commit value on the server -- clients can assume all documents will be commited within that time.
However, this does not help in the case where the clients know what documents need updating quickly and others that could wait. I suggest adding:
{code:xml}
<add commitWithin="100">...
{code}
to the update syntax so the client can schedule commits explicitly.
was:
Currently there are two options for how to handle commiting documents:
1. the client explicitly starts the commit via <commit/>
2. set an auto commit value on the server -- clients can assume all documents will be commited within that time.
However, this does not help in the case where the clients know what documents need updating quickly and others that could wait. I suggest adding:
{code:xml}
<add commitWithin="100">...
{/code:xml}
to the update syntax so the client can schedule commits explicitly.
> set a commit time bounds in the <add> command
> ---------------------------------------------
>
> Key: SOLR-793
> URL: https://issues.apache.org/jira/browse/SOLR-793
> Project: Solr
> Issue Type: Improvement
> Components: update
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 1.4
>
> Attachments: SOLR-793-commitWithin.patch, SOLR-793-commitWithin.patch, SOLR-793-deadlock.patch
>
>
> Currently there are two options for how to handle commiting documents:
> 1. the client explicitly starts the commit via <commit/>
> 2. set an auto commit value on the server -- clients can assume all documents will be commited within that time.
> However, this does not help in the case where the clients know what documents need updating quickly and others that could wait. I suggest adding:
> {code:xml}
> <add commitWithin="100">...
> {code}
> to the update syntax so the client can schedule commits explicitly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.