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 if suddenly we ascribe meaning to it, so I'll let some folks with more native client history than I chime in.
Thanks, Blake On Fri, Dec 13, 2019 at 3:15 AM Alberto Gomez <alberto.go...@est.tech> wrote: > 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 analysis to see if I am in the > right track or if I am missing something. > > Thanks in advance, > > Alberto >
