[
https://issues.apache.org/jira/browse/CASSANDRA-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208787#comment-13208787
]
paul cannon commented on CASSANDRA-3874:
----------------------------------------
Changes made in my 3874-1.0 branch at github:
https://github.com/thepaul/cassandra/tree/3874-1.0
Since the merge forward is not completely trivial, my 3874-1.1 branch has those
commits already merged to 1.1:
https://github.com/thepaul/cassandra/tree/3874-1.1 , and it will be an easy
merge from that to your updated cassandra-1.1, whatever it is.
I'll attach patch versions too, in case you still prefer those.
> 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
>
>
> 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
