[
https://issues.apache.org/jira/browse/CASSANDRA-10650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989892#comment-14989892
]
Andy Tolbert commented on CASSANDRA-10650:
------------------------------------------
It doesn't matter too much, we had already made the change to accommodate this
in the nodejs driver, if user retrieves a UDAs metadata using the drivers API
the initcond field is now a string rather then the associated type. Previously
were were able to grok the type and properly parse so it seems like a loss of
functionality, even if minor.
> 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)
