[
https://issues.apache.org/jira/browse/CASSANDRA-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788334#action_12788334
]
Eric Evans commented on CASSANDRA-619:
--------------------------------------
The problem is that SSTable/SSTableReader assumes that it can suss out the
keyspace name from the full path to the sstable file (see
parseTableName(String)).
Documenting the import/export utilities on the Operations wiki page is on my
short list. Do you think that will suffice?
> sstable2json makes assumption for keyspace
> ------------------------------------------
>
> Key: CASSANDRA-619
> URL: https://issues.apache.org/jira/browse/CASSANDRA-619
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Chris Goffinet
> Assignee: Eric Evans
> Priority: Trivial
> Fix For: 0.5
>
>
> Right now sstable2json makes the assumption that Keyspace folder is one
> parent above. When copying SSTables over to another machine to verify some
> things, it wasn't clear this is how it worked until looking at source code.
> It kept complaining about NullPointerException when trying to lookup an
> invalid keyspace. Can we be more explicit in this error message and ability
> to specify a keyspace name?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
