incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aaron morton <aa...@thelastpickle.com>
Subject Re: readable (not hex encoded) column names using sstable2json
Date Wed, 24 Apr 2013 03:36:33 GMT
What the CF definition ?
What are the errors you are getting?

> We're trying to move data over to another cluster but this prevents us from doing so.

Is there a reason you are converting the SSTables to JSON ? 
You could just copy the sstables. 

Cheers

-----------------
Aaron Morton
Freelance Cassandra Consultant
New Zealand

@aaronmorton
http://www.thelastpickle.com

On 23/04/2013, at 9:37 PM, Hans Melgers <Hans.Melgers@anachron.com> wrote:

> Hello,
> 
> Using Cassandra 1.0.7 sstable2json on some tables I get readable column
> names. This leads to problems (java.lang.NumberFormatException: Non-hex
> characters in) when importing later.
> 
> We're trying to move data over to another cluster but this prevents us
> from doing so. Could it have to do with using a custom Serializer<T>?
> 
> Here example output:
> 
> D:\Java\apache-cassandra-1.0.7\bin>sstable2json
> d:\var\lib\cassandra\data2\depsi\ACCOUNT_RECEIVERS-hc-1-Data.db
> {
> "23696423656139323162633138666635343135616161336136373337666639623038633
> 9": [["dep.1205050","",1364383456519006]],
> "23696423396338306562366366383365346162383863623266663830663863643930343
> 2": [["dep.1057162","",1364383456664000]],
> [GOES ON here]
> 
> The value "dep.1205050" is literally what we put in there. It's not hex
> encoded.
> 
> Kind regards,
> Hans Melgers
> 
> 
> 


Mime
View raw message