Exclude append-increments from tx changeset

as per comment & disccusion - there's nothing to do here

I see the status is in in progress? Which release are we targeting this?

We need first make NONE conflict level truly available for usage before documenting how it can be used with append increments

Heh. It looks like it may not be good idea to remove increments from conflict detection. The level of conflict detection that we provide is "if two concurrent tx modified the same item only one will succeed". App logic may rely on this to e.g. make sure some invariant remains after ops are performed: e.g. account balance will not go over the credit limit. If app logic does withdraw using "readless increments" it expects that the invariant will not be broken as the logic checks the number and then does increment.

So, we can't actually exclude increments from tx conflict detection without changing the guarantees we provide (level of conflict detection). Instead, what we can say is you can safely use ConflictLevel.NONE with readless increments - it will not cause an error in counting (even if same counter is changed by two concurrent transactions).

I'll think more and this will probably result in docs change.