[jira] Commented: (SOLR-793) set a commit time bounds in the command

["Noble Paul (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657757#action_12657757 ] 

Noble Paul commented on SOLR-793:
---------------------------------

The XML API looks a bit ugly.
Why do we need to add this like this <add commitWithin="6">

One update request will have only one <add> . So it could have very well been added to the request params like waitFlush and waitSearcher.

If at all it has to be kept in the xml it should be on a per document .

The SolrInputDocument can have a 'commitWithin' attribute.





> 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: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.