with TransactionIds managed by CacheTransactionManager in
C++ native client
Transactions are an area of the codebase I've never dealt with, so I'm sure
most/all of what you mention is true. In particular, the only thing I know
about TransactionId is that it's always set to -1,
Transactions are an area of the codebase I've never dealt with, so I'm sure
most/all of what you mention is true. In particular, the only thing I know
about TransactionId is that it's always set to -1, so functionally it's
essentially useless. I'm not certain what all of the implications will be
Hi,
I have created a ticket with some issues I have found related to TransactionIds
managed by CacheTransactionManager in the C++ native client.
https://issues.apache.org/jira/browse/GEODE-7573
In it, I also propose some solutions to the issues found.
I'd appreciate if someone could review the
