Add missing type for <blockfor> in protocol specs

This commit is contained in:
Tyler Hobbs 2015-05-12 16:21:58 -05:00
parent 33cf701d1d
commit 28cfbfa685
2 changed files with 10 additions and 10 deletions

View File

@ -683,8 +683,8 @@ Table of Contents
the exception.
<received> is an [int] representing the number of nodes having
acknowledged the request.
<blockfor> is the number of replica whose acknowledgement is
required to achieve <cl>.
<blockfor> is an [int] representing the number of replica whose
acknowledgement is required to achieve <cl>.
<writeType> 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.
<received> is an [int] representing the number of nodes having
answered the request.
<blockfor> is the number of replica whose response is
required to achieve <cl>. Please note that it is
possible to have <received> >= <blockfor> if
<blockfor> is an [int] representing the number of replicas whose
response is required to achieve <cl>. Please note that it
is possible to have <received> >= <blockfor> if
<data_present> is false. And also in the (unlikely)
case were <cl> is achieved but the coordinator node
timeout while waiting for read-repair

View File

@ -867,8 +867,8 @@ Table of Contents
the exception.
<received> is an [int] representing the number of nodes having
acknowledged the request.
<blockfor> is the number of replica whose acknowledgement is
required to achieve <cl>.
<blockfor> is an [int] representing the number of replica whose
acknowledgement is required to achieve <cl>.
<writeType> 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.
<received> is an [int] representing the number of nodes having
answered the request.
<blockfor> is the number of replica whose response is
required to achieve <cl>. Please note that it is
possible to have <received> >= <blockfor> if
<blockfor> is an [int] representing the number of replica whose
response is required to achieve <cl>. Please note that it
is possible to have <received> >= <blockfor> if
<data_present> is false. And also in the (unlikely)
case were <cl> is achieved but the coordinator node
timeout while waiting for read-repair