[
https://issues.apache.org/jira/browse/CASSANDRA-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
paul cannon resolved CASSANDRA-4582.
------------------------------------
Resolution: Won't Fix
I'd like to implement this fix, but it's a little less trivial than it sounds
to do this in a general way for all comparator classes- cqlsh needs to decode
the binary column names according to the comparator class (easy), and then
translate the native python values back into a textual format that CQL will
parse correctly for a value of the original class (not as easy).
The machinery to do that sort of thing is in the trunk (1.2) branch, but it's
not in 1.1, and since this only applies to certain cql2 cases, it doesn't seem
like it would be as useful to put only in cassandra 1.2. Affecting the
usefulness even further is the fact that it seems to be rare to put explicit
column names in a cfdef's column_metadata when the column names use a
non-textual comparator type (where one usually uses wide rows, not pre-defined
columns).
I could backport the more powerful translation machinery to 1.1, but it would
aggravate the already-somewhat-hairy merging situation for cqlsh.
We could also just make this change for comparator=blob and not for the others,
but it doesn't seem clear to me that this would be any more useful for blob
than, say, timeuuid or float or whatever.
Therefore, I'll close this ticket for now; if anyone still feels strongly about
the need and has more convincing input on use cases, we can open it back up.
> in cqlsh the output of describe columnfamily doesn't convert to hex
> -------------------------------------------------------------------
>
> Key: CASSANDRA-4582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4582
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jeremy Hanna
> Assignee: paul cannon
> Priority: Minor
> Labels: cqlsh
>
> When the comparator=blob, cqlsh is outputting the metadata for column names
> in utf8. Instead it should output them in hex because that's what will make
> it so its output can be used to re-create the column family. Granted it's
> going to be pretty unreadable for the user, but it will work to re-create the
> CF.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
