[ https://issues.apache.org/jira/browse/CASSANDRA-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870149#action_12870149 ]
Stu Hood commented on CASSANDRA-912: ------------------------------------ +1 on the idea of tearing out the current CLI and replacing it with a dynamic language shell, possibly with a blessed Thrift wrapper client imported. > First-class commandline interface > --------------------------------- > > Key: CASSANDRA-912 > URL: https://issues.apache.org/jira/browse/CASSANDRA-912 > Project: Cassandra > Issue Type: Improvement > Components: Tools > Affects Versions: 0.6 > Reporter: Eric Evans > > While a useful tool for education and simple tests, cassandra-cli is > ultimately limted by the fact that column names and values are binary, (and > eventually keys will be as well, see CASSANDRA-767). > The current approach when writing consists of encoding column names as UTF8, > and passing the value as a byte[] of the String parsed from the command. When > performing a read, the column names outputted are the result of the > toString() method of the comparator (the result of which is not always > meaningful), and values are again treated as raw strings. This is almost > certainly broken anywhere that the CF comparator is not UTF8Type and values > are anything but strings. > One possible approach would be to follow HBase's lead and simply allow binary > values to be encoded as strings (see: > http://wiki.apache.org/hadoop/Hbase/Shell). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.