[
https://issues.apache.org/jira/browse/CASSANDRA-10650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989901#comment-14989901
]
Aleksey Yeschenko commented on CASSANDRA-10650:
-----------------------------------------------
Got it. Honestly, I really believe that losing that minor bit of functionality
is fine, it's better than adding extra complication to server's schema handling
code. Protocol version-dependency is not something I want to have there.
> 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)
