[
https://issues.apache.org/jira/browse/SOLR-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637114#action_12637114
]
Ryan McKinley commented on SOLR-793:
------------------------------------
perhaps it is better to think of it as selectivly enabling the autoCommit
feature.
bq. If I have 10 docs with with a commitWithin="100" This may mean that there
will be 10 commits because each <add> happened at different time.
assuming the last of the 10 docs were sent to solr within 100ms, then all of
them would be committed at once. The commtWithin time is a *maximum* time, not
a minimum.
This is identical to how autoCommit works now -- the advantage is that various
documents could require different time bounds.
> 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
> 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.
