This answer can help you if you do not need a technical build from the source code, and if you are just starting with a new installation of Cassandra, and not updating the existing one.
I had the same problem when building from source code. To get around this, I used the development construct from the "Latest Builds (Hudson)" link http://cassandra.apache.org/download/ here.
The next problem that you will encounter is that no clusters will be installed during the new installation. To get around this problem, you can use the latest version 0.6.3. This solution did not work for me because I wanted to use Pycassa, which needs 0.7.
So I needed to take the following steps:
Launch the JMX console. Personally, I do not have a server running Cassandra, so I needed to use ssh tunnels, for example:
jconsole -J-DsocksProxyHost = localhost -J-DsocksProxyPort = 1080
Then used this funky URL to connect:
service: jmx: rmi: /// jndi / rmi: //my.hostname.com: 8080 / jmxrmi
Then on the left side
- expand org.apache.cassandra.service
- expand Storage Service expand Operations
- select loadSchemaFromYAML
- In the upper right corner, click the loadSchemaFromYAML button to call it.
You can use the same steps to add new keyspaces during development as soon as you figure out how you want your circuit to look. But the above steps only work if you have no data. Thus, you must delete all your data using rm / var / lib / cassandra / * after removing the server. (Of course, you can take other steps that are harder to transfer data without destroying them.)
I understand that you did not ask about creating key spaces, but in the trunked version of cassandra, if you are just starting out, that will be the next problem. I just spent the day deciding this and hope this helps.
source share