You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@cassandra.apache.org by Chris Beaumont <dr...@yahoo.com> on 2010/04/14 18:53:30 UTC

Did 0.6 break sstable2jason? or am I missing something?

I enjoy very much being able to quickly get a peak at my data once stored, and so
far sstable2json was a great help...

I just completed switching from 0.5.1 to 0.6, and here is what I am getting now:
$ sstable2json Standard2-1-Index.db 
Exception in thread "main" java.lang.NullPointerException
        at java.util.Arrays$ArrayList.<init>(Arrays.java:3357)
        at java.util.Arrays.asList(Arrays.java:3343)
        at org.apache.cassandra.tools.SSTableExport.export(SSTableExport.java:255)
        at org.apache.cassandra.tools.SSTableExport.export(SSTableExport.java:299)
        at org.apache.cassandra.tools.SSTableExport.export(SSTableExport.java:323)
        at org.apache.cassandra.tools.SSTableExport.main(SSTableExport.java:367)

On the other end, sstablekeys seems to still be doing the right thing:
$ sstablekeys Standard2-1-Index.db 
newone

This is on a Centos5 install with
$ java -version
java version "1.6.0_19"

Can anyone reproduce this? or am I missing something?

TIA

Chris.

Re: Did 0.6 break sstable2jason? or am I missing something?

Posted by Brandon Williams <dr...@gmail.com>.

On Wed, Apr 14, 2010 at 11:53 AM, Chris Beaumont <dr...@yahoo.com>wrote:

> I enjoy very much being able to quickly get a peak at my data once stored,
> and so
> far sstable2json was a great help...
>
> I just completed switching from 0.5.1 to 0.6, and here is what I am getting
> now:
> $ sstable2json Standard2-1-Index.db
> Exception in thread "main" java.lang.NullPointerException
>

This was a regression introduced as part of
https://issues.apache.org/jira/browse/CASSANDRA-843 and is fixed in
https://issues.apache.org/jira/browse/CASSANDRA-934

Until 0.6.1 is released, you can work around the NPE by passing -x "" to
sstable2json.

-Brandon