cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Alves (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-2181) sstable2json should return better error message if the usage is wrong
Date Thu, 21 Jun 2012 05:50:43 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398205#comment-13398205
] 

David Alves edited comment on CASSANDRA-2181 at 6/21/12 5:50 AM:
-----------------------------------------------------------------

i'm not able to reproduce the issue.
the only error I'm hitting is a malformed hex key and that one is pretty clear.
I've tried passing a missing key and an existing one as argument and both times the exporter
does what it should.

the patch changes usage and adds a check to avoid letting the user use -k and -x at the same
time

Shotaro Kamio: could you help me to try and figure it out? can you still reproduce this error?
                
      was (Author: dr-alves):
    i'm not able to reproduce the issue.
the only error I'm hitting is a malformed hex key and that one is pretty clear.
I've tried passing a missing key and an existing one as argument and both times the exporter
does what it should.

the patch changes usage and adds a check to avoid letting the user use -k and -x at the same
time
                  
> sstable2json should return better error message if the usage is wrong
> ---------------------------------------------------------------------
>
>                 Key: CASSANDRA-2181
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2181
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>         Environment: linux
>            Reporter: Shotaro Kamio
>            Assignee: David Alves
>            Priority: Minor
>             Fix For: 1.2
>
>         Attachments: 2181.patch
>
>
> These errors are not user friendly.
> (Cassandra 0.7.2)
> $ bin/sstable2json PATH_TO/Order-f-7-Data.db -k aaaaaaa -x 0
>  WARN 21:55:34,383 Schema definitions were defined both locally and in cassandra.yaml.
Definitions in cassandra.yaml were ignored.
> {
> "aaaaaaa": {Exception in thread "main" java.lang.NullPointerException
> 	at org.apache.cassandra.db.columniterator.SSTableSliceIterator.hasNext(SSTableSliceIterator.java:108)
> 	at org.apache.cassandra.tools.SSTableExport.serializeRow(SSTableExport.java:178)
> 	at org.apache.cassandra.tools.SSTableExport.export(SSTableExport.java:310)
> 	at org.apache.cassandra.tools.SSTableExport.main(SSTableExport.java:444)
> $ bin/sstable2json PATH_TO/Order-f-7-Data.db -k aaaaaaa 
>  WARN 21:55:49,603 Schema definitions were defined both locally and in cassandra.yaml.
Definitions in cassandra.yaml were ignored.
> Exception in thread "main" java.lang.NullPointerException
> 	at org.apache.cassandra.tools.SSTableExport.export(SSTableExport.java:284)
> 	at org.apache.cassandra.tools.SSTableExport.main(SSTableExport.java:444)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message