[
https://issues.apache.org/jira/browse/CASSANDRA-10650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989867#comment-14989867
]
Andy Tolbert commented on CASSANDRA-10650:
------------------------------------------
This change can be somewhat breaking/loss of functionality since not all of the
drivers have the capability to parse a text in their deserializers to the
expected types, but they all have and need the capability to parse bytes. The
java driver does have this capability, but the nodejs driver doesn't for
example. Implementing a {{cqltype.decode(text) -> instanceoflangtype}} in
each driver for this would be a non-trivial amount of work just to support
properly parsing initcond. In the nodejs driver we are currently opting to
have 'initcond' in our metadata classes to return a text, but it would be nice
if we could return the actual type (as it did previously). Could we have 2
separate columns (initcond and initcond_literal like you mentioned in
CASSANDRA-10365) for this?
> 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)
