[
https://issues.apache.org/jira/browse/CASSANDRA-14541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17267792#comment-17267792
]
Sam Tunnicliffe commented on CASSANDRA-14541:
---------------------------------------------
[~mck] your patch LGTM. FTR, the ordering of tracing ID and warnings was
specified in section 2.2 (flags), but the position of custom payload was still
potentially ambiguous so I've added some text to clean that up. This affects
both protocol v4 and v5 specs, so I've pushed modified versions of both
[here|https://github.com/beobal/cassandra/commit/219ee43af65690131fa87829e7d43558f20f1474].
If they look right to you, I'll commit them to the appropriate branches.
> Order of warning and custom payloads is unspecified in the protocol
> specification
> ---------------------------------------------------------------------------------
>
> Key: CASSANDRA-14541
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14541
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Documentation and Website
> Reporter: Avi Kivity
> Assignee: Avi Kivity
> Priority: Low
> Fix For: 3.11.x, 4.x
>
> Attachments:
> v1-0001-Document-order-of-tracing-warning-and-custom-payl.patch
>
>
> Section 2.2 of the protocol specification documents the types of tracing,
> warning, and custom payloads, but does not document their order in the body.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
