This does highlight that rollback is perfectly reasonable for embedded Solr
or other "dedicated", single-node, well-controlled apps, even if it doesn't
work for cloud.
-- Jack Krupansky
-----Original Message-----
From: Mark Miller
Sent: Thursday, May 09, 2013 1:09 PM
To: dev@lucene.apache.org
Subject: Re: [Discussion] Discontinue the ROLLBACK command in Solr?
RAMbuffer doesn't affect this stuff - if you rollback, it rolls back to the
last commit point. Flushed segments are fine.
- Mark
On May 9, 2013, at 12:54 PM, Mikhail Khludnev <mkhlud...@griddynamics.com>
wrote:
Jan,
Could you please clarify current rollback functionality to me? Let's I
have autoCommit disabled, but my RAMbuffer is not huge, hence I have few
flushes after previous commit. if I invoke rollback will it forget about
flushed segments?
On Thu, May 2, 2013 at 12:38 AM, Jan Høydahl <jan....@cominvent.com>
wrote:
Hi,
Many are confused about the rollback feature in Solr, since it cannot
guarantee a rollback of updates from that client since last commit.
In my opinion it is pretty useless to have a rollback feature you cannot
rely upon - Unless, that is, you are the only client for sure, having no
autoCommit, and a huge RAMbuffer.
So why don't we simply deprecate the feature in 4.x and remove it from
5.0?
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
Solr Training - www.solrtraining.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
--
Sincerely yours
Mikhail Khludnev
Principal Engineer,
Grid Dynamics
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
