cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <>
Subject Re: Changing the CLI, not a great idea!
Date Thu, 28 Jul 2011 12:46:16 GMT
It defaults to hex because that is how bytestype is represented.  The
default remains bytestype to provide the kind of backwards
compatibility you are complaining about. :)

On Thu, Jul 28, 2011 at 6:56 AM, Edward Capriolo <> wrote:
> On Thursday, July 28, 2011, Sasha Dolgy <> wrote:
>> Unfortunately, the perception that I have as a business consumer and
>> night-time hack, is that more importance and effort is placed on
>> ensuring information is up to date and correct on the
>> website and less on keeping the
>> wiki up to date or relevant... which forces people to be introduced to
>> a for-profit company to get relevant information ... which just so
>> happens to employ a substantial amount of Apache Cassandra
>> contributors ... not that there's anything wrong with that, right?
>> On Thu, Jul 28, 2011 at 10:46 AM, David Boxenhorn <>
>> wrote:
>>> This is part of a much bigger problem, one which has many parts, among
>>> them:
>>> 1. Cassandra is complex. Getting a gestalt understanding of it makes me
>>> think I understand how Alzheimer's patients must feel.
>>> 2. There is no official documentation. Perhaps everything is out there
>>> somewhere, who knows?
>>> 3. Cassandra is a moving target. Books are out of date before they hit
>>> the
>>> press.
>>> 4. Most of the important knowledge about Cassandra exists in a kind of
>>> oral
>>> history, that is hard to keep up with, and even harder to understand once
>>> it's long past.
>>> I think it is clear that we need a better one-stop-shop for good
>>> documentation. What hasn't been talked about much - but I think it's just
>>> as
>>> important - is a good one-stop-shop for Cassandra's oral history.
>>> (You might think this list is the place, but it's too noisy to be useful,
>>> except at the very tip of the cowcatcher. Cassandra needs a canonized
>>> version of its oral history.)
> Well the problem is not lack of documentation but changing things that
> probably do not matter and thus invalidating all documentation.
> To stay on point. Why does the cli default to hex. Come on who is doing
> inserts in hex? Would it be more.natural for the cli to so this:
> 'ascii' auto function call ascii
> "utf8" auto function utf8
> Oxafaf auto function hex
> Or really do not change get add a new statement
> Typedget
> And leave get alone
> The argument to have two methods that almost do the same thing is a bad one,
> but it is no worse then invalidating tons of docs. But really I can't
> support a hex default, I know no one with a hex keyboard.

Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support

View raw message