bq: why we need explicit Commit!! Because the commit is what closes index segments and (optionally) opens a new searcher making documents visible. And because the commit (openSearcher = true|false) is what writes documents durably to the index. And you want to be able to control these operations.
Best Erick On Fri, May 3, 2013 at 7:06 AM, Shekar R (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/SOLR-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648427#comment-13648427 > ] > > Shekar R commented on SOLR-4783: > -------------------------------- > > If there is no Rollback feature... why we need explicit Commit!! > >> Rollback is not working in SolrCloud >> ------------------------------------ >> >> Key: SOLR-4783 >> URL: https://issues.apache.org/jira/browse/SOLR-4783 >> Project: Solr >> Issue Type: Bug >> Components: SolrCloud >> Affects Versions: 4.2.1 >> Environment: AWS Instance >> Linux OS >> Reporter: Shekar R >> Labels: features >> Fix For: 4.2.1 >> >> >> I have 4 Solr 4.2.1 and 3 zookeeper cluster with frontend haproxy to Solr >> instances. >> 1. Add a doc (without inline commit and autocommit is disabled in >> solrconfig.xml) >> 2. Issue rollback. >> 3. Again add another doc. >> 4. Issue commit. >> Both docs will be committed. > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA administrators > For more information on JIRA, see: http://www.atlassian.com/software/jira > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
