From: Timo Sirainen <timo.sirainen@open-xchange.com>
Date: Thu, 28 Nov 2019 19:23:15 +0000 (+0200)
Subject: cassandra: Handle CASS_ERROR_SERVER_WRITE_FAILURE also as "uncertain write"
X-Git-Tag: 2.3.10~195
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=75ac3b5ded877e843a551b32dc349d94afe1118e;p=thirdparty%2Fdovecot%2Fcore.git

cassandra: Handle CASS_ERROR_SERVER_WRITE_FAILURE also as "uncertain write"

This error apparently doesn't happen often, but it seems to be a per-node
failure so some Cassandra nodes could have written the change.
---

diff --git a/src/lib-sql/driver-cassandra.c b/src/lib-sql/driver-cassandra.c
index daddaeca3c..4d691e3aaa 100644
--- a/src/lib-sql/driver-cassandra.c
+++ b/src/lib-sql/driver-cassandra.c
@@ -1157,6 +1157,7 @@ static void query_callback(CassFuture *future, void *context)
 		   not. Also _SERVER_UNAVAILABLE could have actually written
 		   enough copies of the data for the query to succeed. */
 		result->api.error_type = error == CASS_ERROR_SERVER_WRITE_TIMEOUT ||
+			error == CASS_ERROR_SERVER_WRITE_FAILURE ||
 			error == CASS_ERROR_SERVER_UNAVAILABLE ||
 			error == CASS_ERROR_LIB_REQUEST_TIMED_OUT ?
 			SQL_RESULT_ERROR_TYPE_WRITE_UNCERTAIN :