You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Shotaro Kamio (JIRA)" <ji...@apache.org> on 2011/02/17 14:03:24 UTC

[jira] Created: (CASSANDRA-2181) sstable2json should return better error message if the usage is wrong

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: Bug
          Components: Tools
    Affects Versions: 0.7.2
         Environment: linux
            Reporter: Shotaro Kamio
            Priority: Minor


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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Comment Edited] (CASSANDRA-2181) sstable2json should return better error message if the usage is wrong

Posted by "David Alves (JIRA)" <ji...@apache.org>.
    [ 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:43 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
                
      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.

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

        

[jira] [Updated] (CASSANDRA-2181) sstable2json should return better error message if the usage is wrong

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-2181:
--------------------------------------

             Reviewer: yukim
    Affects Version/s:     (was: 0.7.2)
        Fix Version/s: 1.2
             Assignee: David Alves  (was: Benjamin Coverston)
           Issue Type: Improvement  (was: Bug)
    
> 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
>
>
> 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

        

[jira] [Comment Edited] (CASSANDRA-2181) sstable2json should return better error message if the usage is wrong

Posted by "David Alves (JIRA)" <ji...@apache.org>.
    [ 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

        

[jira] [Updated] (CASSANDRA-2181) sstable2json should return better error message if the usage is wrong

Posted by "David Alves (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Alves updated CASSANDRA-2181:
-----------------------------------

    Attachment: 2181.patch
    
> 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

        

[jira] [Commented] (CASSANDRA-2181) sstable2json should return better error message if the usage is wrong

Posted by "David Alves (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13406013#comment-13406013 ] 

David Alves commented on CASSANDRA-2181:
----------------------------------------

Shotaro, any news on this?
                
> 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

        

[jira] Assigned: (CASSANDRA-2181) sstable2json should return better error message if the usage is wrong

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis reassigned CASSANDRA-2181:
-----------------------------------------

    Assignee: Benjamin Coverston

Options handling in SSTableExport could use an overhaul in general, e.g. it doesn't make sense to accept both a list of keys to include, and a list to exclude in the same job.

> 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: Bug
>          Components: Tools
>    Affects Versions: 0.7.2
>         Environment: linux
>            Reporter: Shotaro Kamio
>            Assignee: Benjamin Coverston
>            Priority: Minor
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira