[
https://issues.apache.org/jira/browse/CASSANDRA-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208800#comment-13208800
]
paul cannon commented on CASSANDRA-3874:
----------------------------------------
I think it's worth having in 1.0, especially if it's going to live for a few
more releases. It's technically only a bugfix. But I don't mind much, whichever.
> cqlsh: handle situation where data can't be deserialized as expected
> --------------------------------------------------------------------
>
> Key: CASSANDRA-3874
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3874
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Reporter: paul cannon
> Assignee: paul cannon
> Priority: Minor
> Labels: cqlsh
> Fix For: 1.0.8
>
> Attachments: 3874-1.0.patch.txt, 3874-1.1.patch.txt
>
>
> When cqlsh tries to deserialize data which doesn't match the expected type
> (either because the validation type for the column/key alias was changed, or
> ASSUME has been used), it just fails completely and in most cases won't show
> any results at all. When there is only one misbehaving value out of a large
> number, this can be frustrating.
> cqlsh should either show some failure marker in place of the bad value, or
> simply show the bytes along with some indicator of a failed deserialization.
--
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
