[
https://issues.apache.org/jira/browse/CASSANDRA-13986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov resolved CASSANDRA-13986.
-------------------------------------
Resolution: Fixed
> Fix native protocol v5 spec for new_metadata_id position in Rows response
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-13986
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13986
> Project: Cassandra
> Issue Type: Bug
> Reporter: Olivier Michallat
> Assignee: Alex Petrov
> Priority: Trivial
>
> There's a mistake in the protocol specification for CASSANDRA-10786. In
> `native_protocol_v5.spec`, section 4.2.5.2:
> {code}
> 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>]
> {code}
> The last line should be:
> {code}
>
> <flags><columns_count>[<paging_state>][<new_metadata_id>][<global_table_spec>?<col_spec_1>...<col_spec_n>]
> {code}
> That is, if there is both a paging state and a new metadata id, the paging
> state comes *first*, not second.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
