[
https://issues.apache.org/jira/browse/CASSANDRA-10650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989975#comment-14989975
]
Andy Tolbert commented on CASSANDRA-10650:
------------------------------------------
Sounds good, I think it's ok to not have the byte representation, but just
wanted to indicate the (very) minor loss of functionality. There really isn't
much of a use case that I can think of right now on the client side for parsing
this other than for describe output / recreating the cql schema.
> 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)
