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
Nessie can use retries at the database client level (e.g. with Bigtable) for normal reads.
However, when committing CAS operations (e.g. CheckAndMutateRow in Bigtable) are not idempotent and normally will not retry at the database client level.
Still, Nessie itself can re-attempt the whole commit when the CAS operation is slower than normal. The overhead of rebuilding the commit state is probably negligible in cases when the whole database communication channel slows down.
The text was updated successfully, but these errors were encountered:
Issue description
Nessie can use retries at the database client level (e.g. with Bigtable) for normal reads.
However, when committing CAS operations (e.g.
CheckAndMutateRow
in Bigtable) are not idempotent and normally will not retry at the database client level.Still, Nessie itself can re-attempt the whole commit when the CAS operation is slower than normal. The overhead of rebuilding the commit state is probably negligible in cases when the whole database communication channel slows down.
The text was updated successfully, but these errors were encountered: