Alex Henning Johannessen

I could take a stab at it :)

@alexeyzimarev It seems a bit meaningless to filter out checkpoints with commit != prepare and prepare == 0 as the majority of the checkpoints have prepare == 0 until caughtup....

@alexeyzimarev It might be that I used too few events for my testing and the log positions with prepare 0 I see is from esdb internal events or something like...

> I still don't understand why are you interested in prepare position. My reply was about that. I am not interested in it per say, I wanted to know the...

> Aside from being mysterious, this should work fine as a checkpoint to persist and continue the reads or subscription from later This is what I was fishing a bit...

> Concerning the expected behaviour, unless you are doing explicit transactions (which are only available via the old client), the commit and prepare positions will always be the same. I...

I do not have any actual problem with that as long it is expected that clients can get checkpoints with prepare values with 0. I am just curious about how...

> Unless you are using explicit transactions, they are both the same. This seems not to be the case. I am not using transactions and I get those prepares with...

2.11, 2.12, 2.13 and 3. Personally, I think keeping three supported Scala versions is more than generous. Who is on Scala 2.11 and needs Scala Native 0.5.0? 0.5% of the...

@strelec Right on - and then in addition to that, Scala Native for 2.11.