You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Radim Kolar <hs...@sendmail.cz> on 2011/10/15 14:56:05 UTC
show schema fails
on all nodes in cluster cassandra-0.8.5
[default@rapidshare] show schema;
A long is exactly 8 bytes: 5
how to capture more information for bug report?
Re: show schema fails
Posted by Radim Kolar <hs...@sendmail.cz>.
bug is still there, i opened
https://issues.apache.org/jira/browse/CASSANDRA-3415 with command how to
reproduce.
Re: show schema fails
Posted by aaron morton <aa...@thelastpickle.com>.
I have a vague memory of there been a bug about this in the past.
A
-----------------
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 19/10/2011, at 10:58 PM, Radim Kolar wrote:
> Dne 18.10.2011 22:35, aaron morton napsal(a):
>> Looks like the column meta for the CF specifies a column name that is not a valid Long. I seem to remember a bug like this something in the past.
> but why are columns in system tables untyped? if it was declared as long, its impossible to insert bad value into it.
Re: show schema fails
Posted by Radim Kolar <hs...@sendmail.cz>.
Dne 18.10.2011 22:35, aaron morton napsal(a):
> Looks like the column meta for the CF specifies a column name that is
> not a valid Long. I seem to remember a bug like this something in the
> past.
but why are columns in system tables untyped? if it was declared as
long, its impossible to insert bad value into it.
Re: show schema fails
Posted by aaron morton <aa...@thelastpickle.com>.
Looks like the column meta for the CF specifies a column name that is not a valid Long. I seem to remember a bug like this something in the past.
You should be able to work around this by running ALTER COLUMN FAMILY and only specifying valid column meta data.
Cheers
-----------------
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 18/10/2011, at 6:26 PM, Radim Kolar wrote:
> Dne 17.10.2011 22:06, aaron morton napsal(a):
>> Hi there,
>> If you start cassandra-cli with --debug it will output a stack trace if the error is client side.
> A long is exactly 8 bytes: 5
> java.lang.RuntimeException: A long is exactly 8 bytes: 5
> at org.apache.cassandra.cli.CliClient.executeCLIStatement(CliClient.java:310)
> at org.apache.cassandra.cli.CliMain.processStatement(CliMain.java:217)
> at org.apache.cassandra.cli.CliMain.main(CliMain.java:345)
> Caused by: org.apache.cassandra.db.marshal.MarshalException: A long is exactly 8 bytes: 5
> at org.apache.cassandra.db.marshal.LongType.getString(LongType.java:72)
> at org.apache.cassandra.cli.CliClient.showColumnMeta(CliClient.java:1710)
> at org.apache.cassandra.cli.CliClient.showColumnFamily(CliClient.java:1687)
> at org.apache.cassandra.cli.CliClient.showKeyspace(CliClient.java:1637)
> at org.apache.cassandra.cli.CliClient.executeShowSchema(CliClient.java:1598)
> at org.apache.cassandra.cli.CliClient.executeCLIStatement(CliClient.java:250)
> ... 2 more
>
> No error in server log. cli expect long value but in database is stored something different. it should not be possible to store different type if column has metadata set.
Re: show schema fails
Posted by Radim Kolar <hs...@sendmail.cz>.
Dne 17.10.2011 22:06, aaron morton napsal(a):
> Hi there,
> If you start cassandra-cli with --debug it will output a stack trace if the error is client side.
A long is exactly 8 bytes: 5
java.lang.RuntimeException: A long is exactly 8 bytes: 5
at
org.apache.cassandra.cli.CliClient.executeCLIStatement(CliClient.java:310)
at
org.apache.cassandra.cli.CliMain.processStatement(CliMain.java:217)
at org.apache.cassandra.cli.CliMain.main(CliMain.java:345)
Caused by: org.apache.cassandra.db.marshal.MarshalException: A long is
exactly 8 bytes: 5
at
org.apache.cassandra.db.marshal.LongType.getString(LongType.java:72)
at
org.apache.cassandra.cli.CliClient.showColumnMeta(CliClient.java:1710)
at
org.apache.cassandra.cli.CliClient.showColumnFamily(CliClient.java:1687)
at
org.apache.cassandra.cli.CliClient.showKeyspace(CliClient.java:1637)
at
org.apache.cassandra.cli.CliClient.executeShowSchema(CliClient.java:1598)
at
org.apache.cassandra.cli.CliClient.executeCLIStatement(CliClient.java:250)
... 2 more
No error in server log. cli expect long value but in database is stored
something different. it should not be possible to store different type
if column has metadata set.
Re: show schema fails
Posted by aaron morton <aa...@thelastpickle.com>.
Hi there,
If you start cassandra-cli with --debug it will output a stack trace if the error is client side.
Otherwise check the server log, by default it's in /var/log/cassandra/system.log
Thanks.
-----------------
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 16/10/2011, at 1:56 AM, Radim Kolar wrote:
> on all nodes in cluster cassandra-0.8.5
>
> [default@rapidshare] show schema;
> A long is exactly 8 bytes: 5
>
> how to capture more information for bug report?
>