cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aaron morton <>
Subject Re: show schema fails
Date Tue, 18 Oct 2011 20:35:04 GMT
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. 


Aaron Morton
Freelance Developer

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(
>        at org.apache.cassandra.cli.CliMain.processStatement(
>        at org.apache.cassandra.cli.CliMain.main(
> Caused by: org.apache.cassandra.db.marshal.MarshalException: A long is exactly 8 bytes:
>        at org.apache.cassandra.db.marshal.LongType.getString(
>        at org.apache.cassandra.cli.CliClient.showColumnMeta(
>        at org.apache.cassandra.cli.CliClient.showColumnFamily(
>        at org.apache.cassandra.cli.CliClient.showKeyspace(
>        at org.apache.cassandra.cli.CliClient.executeShowSchema(
>        at org.apache.cassandra.cli.CliClient.executeCLIStatement(
>        ... 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.

View raw message