bug is still there, i opened
https://issues.apache.org/jira/browse/CASSANDRA-3415 with command how to
reproduce.
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
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
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
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
