You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Adam Holmberg (JIRA)" <ji...@apache.org> on 2015/11/04 19:54:28 UTC

[jira] [Comment Edited] (CASSANDRA-10650) Fix INITCOND after 10365

    [ https://issues.apache.org/jira/browse/CASSANDRA-10650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14990170#comment-14990170 ] 

Adam Holmberg edited comment on CASSANDRA-10650 at 11/4/15 6:53 PM:
--------------------------------------------------------------------

Python driver integration tests run cleanly against Robert's latest @ ec655f38


was (Author: aholmber):
Python rc1 integration tests run clean against Robert's latest @ ec655f38

> 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)