Details
-
Improvement
-
Resolution: Won't Fix
-
Major
-
tech-debt
-
DOC-2021-Jun06-S11, DOC-2021-Jun20-S12, DOC-2021-Jul04-S13, DOC-2021-Jul18-S14, DOC-2021-Nov07-S22, DOC-2021-Nov21-S23, DOC-2021-Dec05-S24, DOC-2021-Dec19-S25, DOC-2021-Dec31-S26, DOC-2022-S1, DOC-2022-S2, DOC-2022-S3, DOC-2022-S4, DOC-2022-S5, DOC-2022-S6, DOC-2022-S7, DOC-2022-S8, DOC-2022-S9, DOC-2022-S10, DOC-2022-S11, DOC-2022-S12, DOC-2022-S13, DOC-2022-S14, DOC-2022-S15, DOC-2022-S16, DOC-2022-S17, DOC-2022-S18, DOC-2022-S19
-
1
Description
We should document the fact that queryTxTimeout, specified at the cluster level, acts as a unconditional upper bound on all transactional statements that are executed. This does not match with the existing SDK precedence where overriding timeouts is possible at any level. See the linked TXNJ for additional information.