cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "paul cannon (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3874) cqlsh: handle situation where data can't be deserialized as expected
Date Wed, 15 Feb 2012 23:57:00 GMT


paul cannon commented on CASSANDRA-3874:

updated the 3874-1.1 branch just now to add the 1.0.9 version of the python-cql library, since
that is required for this fix to work. 1.0 doesn't have an embedded python-cql lib, so it's
> cqlsh: handle situation where data can't be deserialized as expected
> --------------------------------------------------------------------
>                 Key: CASSANDRA-3874
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message