When a regular Scan encounters a ReadWithinUncertaintyInterval error, the TxnCoordSender will immediately try to refresh the txn's read spans and, if successful, retry the batch. This doesn't apply to DistSQL reads which don't go through the TxnCoordSender.
We should figure out another level at which to retry.
Separately, if the whole flow is scheduled on the gateway, everything could go through the TxnCoordSender, I think.
Jira issue: CRDB-5744
When a regular Scan encounters a
ReadWithinUncertaintyIntervalerror, theTxnCoordSenderwill immediately try to refresh the txn's read spans and, if successful, retry the batch. This doesn't apply to DistSQL reads which don't go through theTxnCoordSender.We should figure out another level at which to retry.
Separately, if the whole flow is scheduled on the gateway, everything could go through the
TxnCoordSender, I think.Jira issue: CRDB-5744