[CASSANDRA-13986] Fix native protocol v5 spec for new_metadata_id position in Rows response

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Severity: Low
• Assignee: Alex Petrov
• Reporter: Olivier Michallat

Authors

Alex Petrov

• Created: 01/Nov/17 22:24
• Updated: 16/Apr/19 09:29
• Resolved: 08/Nov/17 12:15

Description

There's a mistake in the protocol specification for CASSANDRA-10786. In `native_protocol_v5.spec`, section 4.2.5.2:

4.2.5.2. Rows

  Indicates a set of rows. The rest of the body of a Rows result is:
    <metadata><rows_count><rows_content>
  where:
    - <metadata> is composed of:
        <flags><columns_count>[<new_metadata_id>][<paging_state>][<global_table_spec>?<col_spec_1>...<col_spec_n>]

The last line should be:

        <flags><columns_count>[<paging_state>][<new_metadata_id>][<global_table_spec>?<col_spec_1>...<col_spec_n>]

That is, if there is both a paging state and a new metadata id, the paging state comes first, not second.

Issue Links

• relates to: CASSANDRA-10786 Include hash of result set metadata in prepared statement id