Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of edlinuxguru@gmail.com
 designates 209.85.210.172 as permitted sender)
MIME-Version: 1.0
Date: Wed, 27 Jul 2011 23:53:42 -0400
Message-ID: 
 <CAENxBwweZYjxtRm1PB9USzadBxktgTMiWwssrA4BgMTtWHDz8A@mail.gmail.com>
Subject: Changing the CLI, not a great idea!
From: Edward Capriolo <edlinuxguru@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=20cf307f33d067c93304a9191cf4

--20cf307f33d067c93304a9191cf4
Content-Type: text/plain; charset=ISO-8859-1

Notice how users react to these things. At one point for example we decided
to add a ';' to the CLI.

http://www.amazon.com/Cassandra-Definitive-Guide-Eben-Hewitt/dp/1449390412

The initial chapters on downloading and installing the product get the
reader started using Cassandra immediately. Then the bumps in the road
appear. The current version of Cassandra requires a semicolon to end each
statement in the command line interface (CLI) client - that 's missing in
the book. This is noted in the errata on the O'Reilly site as "unconfirmed",
and if you're coming from a MySQL/Oracle background it's something you might
try, otherwise, it's frustrating.

It confuses users and here is the kicker:

[default@app] use app; use app;
Syntax error at position 9: missing EOF at 'use'

You can not even put two statements on the same line. So the ';' is semi
useless syntax.

What have learned we learned from this?

[default@app] set people['ecapriolo']['last']='capriolo';
org.apache.cassandra.db.marshal.MarshalException: cannot parse 'last' as hex
bytes

Ow dear... are you saying...
[default@app] set
people[ascii('ecapriolo')][ascii('last')]=ascii('capriolo');
Value inserted.

Is their a way to move things forward without hurting backwards
compatibility of the CLI?

Edward

--20cf307f33d067c93304a9191cf4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Notice how users react to these things. At one point for example we decided=
 to add a &#39;;&#39; to the CLI.<br><br><a href=3D"http://www.amazon.com/C=
assandra-Definitive-Guide-Eben-Hewitt/dp/1449390412">http://www.amazon.com/=
Cassandra-Definitive-Guide-Eben-Hewitt/dp/1449390412</a><br>
<br>The initial chapters on downloading and installing the product get=20
the reader started using Cassandra immediately.  Then the bumps in the=20
road appear.  The current version of Cassandra requires a semicolon to=20
end each statement in the command line interface (CLI) client - that &#39;s=
=20
missing in the book.  This is noted in the errata on the O&#39;Reilly site=
=20
as &quot;unconfirmed&quot;, and if you&#39;re coming from a MySQL/Oracle ba=
ckground=20
it&#39;s something you might try, otherwise, it&#39;s frustrating.
<br><br>It confuses users and here is the kicker:<br><br>[default@app] use =
app; use app;<br>Syntax error at position 9: missing EOF at &#39;use&#39;<b=
r><br>You can not even put two statements on the same line. So the &#39;;&#=
39; is semi useless syntax.<br>
<br>What have learned we learned from this?<br><br>[default@app] set people=
[&#39;ecapriolo&#39;][&#39;last&#39;]=3D&#39;capriolo&#39;;=A0=A0=A0=A0=A0=
=A0 <br>org.apache.cassandra.db.marshal.MarshalException: cannot parse &#39=
;last&#39; as hex bytes<br>
<br>Ow dear... are you saying...<br>[default@app] set people[ascii(&#39;eca=
priolo&#39;)][ascii(&#39;last&#39;)]=3Dascii(&#39;capriolo&#39;);<br>Value =
inserted.<br><br>Is their a way to move things forward without hurting back=
wards compatibility of the CLI?<br>
<br>Edward<br>

--20cf307f33d067c93304a9191cf4--