[
https://issues.apache.org/jira/browse/CASSANDRA-10650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989898#comment-14989898
]
Robert Stupp commented on CASSANDRA-10650:
------------------------------------------
Also: byte representation's major disadvantage is that it depends on the
*latest* native protocol version used by the node a driver's currently querying
the schema from. I.e. in the future it would add more burden to the drivers
when the serialized representation changes - up to the probable situation that
an (older) driver version is not able to use the byte representation of a
(newer) C* version correctly.
> Fix INITCOND after 10365
> ------------------------
>
> Key: CASSANDRA-10650
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10650
> Project: Cassandra
> Issue Type: Bug
> Reporter: Robert Stupp
> Assignee: Robert Stupp
> Fix For: 3.0.0
>
>
> CASSANDRA-10365 changed UDA's _initcond_ type to text. That required
> CASSANDRA-10617 to be able to transform the serialized data to a valid CQL3
> literal.
> This ticket is about to fix the _initcond_ thing broken in CASSANDRA-10365
> after CASSANDRA-10617.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
