diff --git a/doc/native_protocol_v1.spec b/doc/native_protocol_v1.spec index 41146f97da..0329765f44 100644 --- a/doc/native_protocol_v1.spec +++ b/doc/native_protocol_v1.spec @@ -683,8 +683,8 @@ Table of Contents the exception. is an [int] representing the number of nodes having acknowledged the request. - is the number of replica whose acknowledgement is - required to achieve . + is an [int] representing the number of replica whose + acknowledgement is required to achieve . is a [string] that describe the type of the write that timeouted. The value of that string can be one of: @@ -709,9 +709,9 @@ Table of Contents the exception. is an [int] representing the number of nodes having answered the request. - is the number of replica whose response is - required to achieve . Please note that it is - possible to have >= if + is an [int] representing the number of replicas whose + response is required to achieve . Please note that it + is possible to have >= if is false. And also in the (unlikely) case were is achieved but the coordinator node timeout while waiting for read-repair diff --git a/doc/native_protocol_v2.spec b/doc/native_protocol_v2.spec index 584ae2f6f5..449396635f 100644 --- a/doc/native_protocol_v2.spec +++ b/doc/native_protocol_v2.spec @@ -867,8 +867,8 @@ Table of Contents the exception. is an [int] representing the number of nodes having acknowledged the request. - is the number of replica whose acknowledgement is - required to achieve . + is an [int] representing the number of replica whose + acknowledgement is required to achieve . is a [string] that describe the type of the write that timeouted. The value of that string can be one of: @@ -893,9 +893,9 @@ Table of Contents the exception. is an [int] representing the number of nodes having answered the request. - is the number of replica whose response is - required to achieve . Please note that it is - possible to have >= if + is an [int] representing the number of replica whose + response is required to achieve . Please note that it + is possible to have >= if is false. And also in the (unlikely) case were is achieved but the coordinator node timeout while waiting for read-repair