Yes, that is correct. --wunder On May 2, 2013, at 7:46 PM, mark12345 wrote:
> Question: Just to clarify. Are you saying that if I have multiple threads > using multiple instances of HttpSolrServer each making calls to add > SolrInputDocuments (For example, "httpSolrServer.add(SolrInputDocument > doc)". ), and one server calls "httpSolrServer.commit()", all documents > added are now commited? > > > If that is the case it does help me understand the rollback api description > in a new light. > > http://lucene.apache.org/solr/4_2_0/solr-solrj/org/apache/solr/client/solrj/SolrServer.html#rollback%28%29 > >> Performs a rollback of all non-committed documents pending. >> >> Note that this is not a true rollback as in databases. Content you have >> previously added may have been committed due to autoCommit, buffer full, >> other client performing a commit etc. > > ---- > > > Michael Della Bitta-2 wrote >> Per core or collection, depending on whether we're talking about Cloud or >> not. >> >> Basically, commits in Solr are about controlling visibility more than >> anything, although now with Cloud, they have resource consumption and >> lifecycle ramifications as well. >> On May 2, 2013 10:01 PM, "mark12345" wrote: >> >>> By saying commits in Solr are "global", do you mean per Solr deployment, >>> per >>> HttpSolrServer instance, per thread, or something else? >>> >>> >>> >>> -- >>> View this message in context: >>> http://lucene.472066.n3.nabble.com/SolrJ-Solr-Two-Phase-Commit-tp4060399p4060584.html >>> Sent from the Solr - User mailing list archive at Nabble.com. >>> > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SolrJ-Solr-Two-Phase-Commit-tp4060399p4060589.html > Sent from the Solr - User mailing list archive at Nabble.com. -- Walter Underwood wun...@wunderwood.org
