On 6/7/2016 12:41 AM, Pithon Philippe wrote:
> I have a question on Solr Transaction as relational databases The Solr
> commit is not isolated for each client session, right? In my test
> (source below) The commit in a session adds records of other sessions
> is there a documentation on this? is wh
Ah, it's easy. It reminds me the fact that ESB don't use transactions in
favor of compansations.
Allocate some txId, assign it on every doc then if you need to rollback
submit deleteByQuery txId:<666>, and commit. Although, it provides phantom
and dirty reads both, it's really cheap. If you need so
There is no equivalent to transactions in Lucene or Solr. A commit
persists newly added documents to disk - all of them, regardless of
which client sent them. A rollback discards all uncommitted documents,
regardless of which client sent them, which renders a rollback pretty
un-useful.
If you need
Hi Pithon,
I have to state beforehand that I worked with transactions on Solr 4.8.1,
so I'm not sure the transactions are changed in Solr over time.
And, I have to add, the transactions support not is very well documented,
so most of what I know is based on my experience.
Given that, Solr clients
Thanks,
my problem is for rollback transaction by user...
if there is a problem in trycatch for a user, the rollback run for all
users commit...
Philippe
2016-06-07 9:23 GMT+02:00 Mikhail Khludnev :
> Hello,
>
> That's how Lucene work underneath.
> Just ad-hoc idea you can have isolated per sessi
Hello,
That's how Lucene work underneath.
Just ad-hoc idea you can have isolated per session indices and then add
them altogether. Thinking deeper, we can consider per thread invertors
which somehow isolated, perhaps something transactional might be built on
top of them, but it's really deep hack.
Hi,
I have a question on Solr Transaction as relational databases
The Solr commit is not isolated for each client session, right?
In my test (source below) The commit in a session adds records of other
sessions
is there a documentation on this?
is what's planned improvements on this? version 6, ve
