[jira] [Commented] (CASSANDRA-4546) cqlsh: handle when full cassandra type class names are given

["Kirk True (JIRA)" <ji...@apache.org>]

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

Kirk True commented on CASSANDRA-4546:
--------------------------------------

+1 on the first part of the patch.

The third change in the patch _appears_ unrelated to me. Please clarify for my own edification.

Thanks.
                
> cqlsh: handle when full cassandra type class names are given
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-4546
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4546
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 1.2.0
>            Reporter: paul cannon
>            Assignee: paul cannon
>              Labels: cqlsh
>             Fix For: 1.2.0
>
>         Attachments: 4546.patch.txt
>
>
> When a builtin Cassandra type was being used for data in previous versions of Cassandra, only the short name was sent: "UTF8Type", "TimeUUIDType", etc. Starting with 1.2, as of CASSANDRA-4453, the full class names are sent.
> Cqlsh doesn't know how to handle this, and is currently treating all data as if it were an unknown type. This goes as far as to cause an exception when the type is actually a number, because the driver deserializes it right, and then cqlsh tries to use it as a string.
> Here for googlage:
> {noformat}
> AttributeError: 'int' object has no attribute 'replace'
> {noformat}
> Fixeries are in order.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira