[
https://issues.apache.org/jira/browse/SOLR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469663
]
Ryan McKinley commented on SOLR-126:
------------------------------------
It looks like the test solrconfi.xml got commited with some mangled xml
comments:
<!-- autocommit pending docs if certain criteria are met
<autoCommit>
<maxDocs>10000</maxDocs>
<maxTime>3600000</maxTime> <!-- one hour in milliseconds -->
</autoCommit>
-->
so it fails the tests
it needs to be:
<!-- autocommit pending docs if certain criteria are met -->
<autoCommit>
<maxDocs>10000</maxDocs>
<maxTime>3600000</maxTime> <!-- one hour in milliseconds -->
</autoCommit>
thanks!
ryan
> 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: AutoCommit.patch, 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.
