[
https://issues.apache.org/jira/browse/SOLR-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved SOLR-793.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.4
Thanks for checking this out Mike.
I changed max time logic to use:
{code:java}
long ctime = (commitWithin>0) ? commitWithin : timeUpperBound;
if( ctime > 0 ) {
scheduleCommitWithin( ctime );
}
{code}
This way, if you have a timeUpperBound set, it will use the passed in argument
rather then the minimum of the two times.
> 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
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
