xtern commented on PR #1501: URL: https://github.com/apache/ignite-3/pull/1501#issuecomment-1408544986
> I don't think we can operate with RAFT terminology in SQL execution layer. Let's think how to avoid using the terms in API methods. Leader and term should be a part of some transactional context, which can be passed through execution layer and indices right down to the tables layer. Agreed, but from my point of view, we are currently blocked by [1] and/or [2] (see TODO in javadoc for ReadWriteReplicaRequest#term). Because when we process the ReadWriteReplicaRequest, the "term" from the request is currently checked (see PartitionReplicaListener#ensureReplicaIsPrimary). It operates with request 'term', but it seems that it should check term from enlisted partitions. So currently we can't do a RW-scan passing only the transaction id (we also need to pass the "term" somehow). @AMashenkov Do you have any idea how to get around this? [1] https://issues.apache.org/jira/browse/IGNITE-17256 [2] https://issues.apache.org/jira/browse/IGNITE-15083 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
