[
https://issues.apache.org/jira/browse/CASSANDRA-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams resolved CASSANDRA-5297.
-----------------------------------------
Resolution: Not A Problem
I think you're speaking about the 1.0 sstableloader. These things were mostly
solved in 1.1 (for instance there's no need to play the loopback game any
longer.)
> sstableloader's interface could be improved
> -------------------------------------------
>
> Key: CASSANDRA-5297
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5297
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Dan Peebles
> Priority: Minor
>
> According to
> http://stackoverflow.com/questions/6832285/how-do-you-use-the-cassandra-tool-sstableloader
> and other references, it looks like running sstableloader in many cases
> necessitates duplicating (a subset of) the destination node's Cassandra
> install folder. This is primarily to have the right cassandra.yaml in the
> right place, as far as I can see.
> It seems like it would be much less of a pain to use the bulk loader if it
> took a parameter for where to look for cassandra.yaml (or supported the
> individual settings it needed to gossip correctly directly on command line)
> The whole business about making a duplicate loopback interface also seems a
> bit Byzantine.
> Since the command-line tool appears just to be a fairly thin wrapper around
> code that is used elsewhere in Cassandra, disentangling it from the standard
> Cassandra configuration might be fairly difficult. But then again I'm pretty
> clueless so I'd be happy to be corrected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
