You might find this useful:
https://lucidworks.com/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/
bq: So I can never have soft auto commit after each update ? This
sounds like a bug to me.
No, rather a fundamental misunderstanding of the difference between an
ACID
On 8/24/2017 4:59 AM, Angel Todorov wrote:
> I also tested, of course, by setting a value of 0, expecting that it would
> work in the way I expect it to , but unfortunately - it doesn't. Nothing is
> committed in that case.
Settings of zero turn that part of the automatic commit off. That's a
way
1. I would call this a bug. It should be equal to or greater than.
2. A design that needs a soft commit after every document is also a bug. That
is big performance hit. Soft commits are cheaper than hard commits, but they
are not free. If you want a commit after every document, use a database. T
Hello,
So I can never have soft auto commit after each update ? This sounds like a
bug to me.
Thanks
Angrl
On Thu, Aug 24, 2017 at 9:36 PM Susheel Kumar wrote:
> I believe the commit triggers on > condition (no of cached docs > maxDocs
> then commit). So that's why you need one extra...
>
> O
I believe the commit triggers on > condition (no of cached docs > maxDocs
then commit). So that's why you need one extra...
On Thu, Aug 24, 2017 at 6:59 AM, Angel Todorov wrote:
> I also tested, of course, by setting a value of 0, expecting that it would
> work in the way I expect it to , but u
I also tested, of course, by setting a value of 0, expecting that it would
work in the way I expect it to , but unfortunately - it doesn't. Nothing is
committed in that case.
Thanks
On Thu, Aug 24, 2017 at 1:54 PM, Angel Todorov wrote:
> Hi all,
>
> I have this in my config:
>
>
>
>
