You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The YDB SDK has a feature in TableTransaction where we can commit a transaction in one query with executeDataQuery. This can save time on network communication if we send this flag instead of a separate commit. For read queries, we can't determine if the query is the last in the transaction or not. However, we have a queue for write queries that executes at the end of user-code transactions, and in this case, we know which query is the last.
The text was updated successfully, but these errors were encountered:
https://github.com/ydb-platform/ydb-java-sdk/blob/develop/table/src/main/java/tech/ydb/table/transaction/TableTransaction.java#L36
The YDB SDK has a feature in TableTransaction where we can commit a transaction in one query with executeDataQuery. This can save time on network communication if we send this flag instead of a separate commit. For read queries, we can't determine if the query is the last in the transaction or not. However, we have a queue for write queries that executes at the end of user-code transactions, and in this case, we know which query is the last.
The text was updated successfully, but these errors were encountered: