You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "paul cannon (Created) (JIRA)" <ji...@apache.org> on 2012/02/08 01:36:59 UTC
[jira] [Created] (CASSANDRA-3874) cqlsh: handle situation where
data can't be deserialized as expected
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
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
[jira] [Commented] (CASSANDRA-3874) cqlsh: handle situation where
data can't be deserialized as expected
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208790#comment-13208790 ]
Jonathan Ellis commented on CASSANDRA-3874:
-------------------------------------------
Is this a big enough change that we should keep it to 1.1 only?
> 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
[jira] [Commented] (CASSANDRA-3874) cqlsh: handle situation where
data can't be deserialized as expected
Posted by "paul cannon (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208983#comment-13208983 ]
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 fine.
> 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
[jira] [Commented] (CASSANDRA-3874) cqlsh: handle situation where
data can't be deserialized as expected
Posted by "paul cannon (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (CASSANDRA-3874) cqlsh: handle situation where
data can't be deserialized as expected
Posted by "paul cannon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon updated CASSANDRA-3874:
-----------------------------------
Attachment: 3874-1.1.patch.txt
3874-1.0.patch.txt
> 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
[jira] [Commented] (CASSANDRA-3874) cqlsh: handle situation where
data can't be deserialized as expected
Posted by "paul cannon (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (CASSANDRA-3874) cqlsh: handle situation where
data can't be deserialized as expected
Posted by "Jonathan Ellis (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-3874:
--------------------------------------
Reviewer: brandon.williams
> 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