[
https://issues.apache.org/jira/browse/CASSANDRA-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-2278.
---------------------------------------
Resolution: Not A Problem
bq. this will work only of all displayed keys conform to the assumption type
This is working as designed. If you want to allow keys of different types,
stick w/ BytesType.
> CLI list <cf> fails when keys are not of the assumed type
> ---------------------------------------------------------
>
> Key: CASSANDRA-2278
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2278
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Affects Versions: 0.7.3
> Reporter: Yaniv Kunda
> Priority: Minor
>
> If a keyspace contains non-utf8 keys (for example, {{LongType}} keys), the
> "{{list <cf>;}}" command can fail converting a key for display, only
> outputting the message "{{Input length = 1}}" and stopping the listing of the
> rest of the keys.
> This message seems to be an example of the standard exception message of
> {{java.nio.charset.MalformedInputException}}.
> Similar messages will probably appear when utf8 keys are assumed to be long,
> etc.
> Workaround: use "{{assume <cf> keys as <type>;}}" - but this will work only
> of all displayed keys conform to the assumption type.
> Suggested fix: If key cannot be converted to the assumption type, instead of
> {{RowKey: <key>}}
> display
> {{RowKey bytes: <keybytes> (cannot convert key to <type>)}}
--
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
