-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is Cassandra 2.0 supported? #26
Comments
Judging from the pom.xml, the answer seems to be no. <properties>
<storm.version>0.8.2</storm.version>
<cassandra.version>1.2.5</cassandra.version>
</properties> Looks like it wants 1.2.5. |
Thanks. I discovered this and went with Cassandra 1.x. It works great, by the way. |
I tried the same but stopped as soon as found that the Netflix Astyanax (which this library uses to write to Cassandra) itself is build with Cassandra 1.2.11 based on this |
You may wan to try storm-cassandra-cql. We are trying to keep that current. |
Hi,
I've been trying to make storm-cassandra version 0.4.0-rc2 work with Cassandra version 2.0 but it doesn't seem to work. It doesn't throw any exceptions, either.
My environment is as follows:
storm-kafka: version 0.9.0-wip16a-scala292
storm: version 0.9.0-wip16
storm-cassandra: version 0.4.0-rc2.
kafka and storm communicates well but storm-cassandra doesn't persist the tuple passed to it to the Cassandra 2.0 database. I've created the KEYSPACE and Column Family in the DB and followed the PersistentWordCount example.
Any advice will be appreciated very much.
Kind Regards.
The text was updated successfully, but these errors were encountered: