From 02f78f658ce96fe2acec903535c3b677d20ee6cb Mon Sep 17 00:00:00 2001 From: Amos Jianjun Kong Date: Sat, 28 May 2016 23:39:43 +0800 Subject: [PATCH] Correct section number of opcode section in protocol spec patch by Amos Jianjun Kong; reviewed by Aleksey Yeschenko for CASSANDRA-11915 --- doc/native_protocol_v3.spec | 2 +- doc/native_protocol_v4.spec | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/native_protocol_v3.spec b/doc/native_protocol_v3.spec index 4876772e41..c38e26cd87 100644 --- a/doc/native_protocol_v3.spec +++ b/doc/native_protocol_v3.spec @@ -65,7 +65,7 @@ Table of Contents Each frame contains a fixed size header (9 bytes) followed by a variable size body. The header is described in Section 2. The content of the body depends on the header opcode value (the body can in particular be empty for some - opcode values). The list of allowed opcode is defined Section 2.3 and the + opcode values). The list of allowed opcode is defined Section 2.4 and the details of each corresponding message is described Section 4. The protocol distinguishes 2 types of frames: requests and responses. Requests diff --git a/doc/native_protocol_v4.spec b/doc/native_protocol_v4.spec index 7fcf1d89c1..1889202551 100644 --- a/doc/native_protocol_v4.spec +++ b/doc/native_protocol_v4.spec @@ -65,7 +65,7 @@ Table of Contents Each frame contains a fixed size header (9 bytes) followed by a variable size body. The header is described in Section 2. The content of the body depends on the header opcode value (the body can in particular be empty for some - opcode values). The list of allowed opcodes is defined in Section 2.3 and the + opcode values). The list of allowed opcodes is defined in Section 2.4 and the details of each corresponding message are described Section 4. The protocol distinguishes two types of frames: requests and responses. Requests