renamed Cassandra into CassandraOld

[calonso]

This PR simply renames the Cassandra symbol into CassandraOld so that this gem can coexist with the newest Cassandra official one from DataStax in the same project.

[calonso]

@psanford Any comments/thoughts about this?

[psanford]

I agree that it would be useful to be able to use both gems at the same time. However, it seems like doing this will break all existing users of the gem.

[calonso]

Agree, then bumping major version and adding a small tutorial with something like:

Find in your project 'Cassandra' and replace with 'CassandraOld'

should fix it, right?
So only people that really needs it update it, and if they do it should be quick.

[psanford]

I'm not comfortable with this change without getting buy-in from some of the other maintainers.

[46labs]

@calonso did you run into an issue with latency when changing the namespace. We didnt see your commit before and modified the namespace from scratch. After that, there is a 5-6 second pause between every query. Its possible it could be because we are trying to hit C* 2.1 with it, but that shouldnt matter. Any ideas?

[calonso]

@46labs Not that I'm aware of, but I remember having a 10 seconds delay on every connection because a removed node hadn't been removed from the peers table of some of the other nodes. I know it has nothing to do with this, but just trying to give ideas. BTW, we discovered that by enabling and reading logging. Maybe if you enable logging you may find out the clue.

[46labs]

Have you ever attempted to use the driver on C* 2.1?

TREVOR FRANCIS
CEO

[email protected] mailto:[email protected]
Toll-Free: +1 (855) GO46LAB
Local: +1 (512) 831-3664

On Jun 23, 2015, at 8:09 AM, Carlos Alonso [email protected] wrote:

@46labs https://github.com/46labs Not that I'm aware of, but I remember having a 10 seconds delay on every connection because a removed node hadn't been removed from the peers table of some of the other nodes. I know it has nothing to do with this, but just trying to give ideas. BTW, we discovered that by enabling and reading logging. Maybe if you enable logging you may find out the clue.

—
Reply to this email directly or view it on GitHub #217 (comment).

[calonso]

No, I haven't our cluster is 1.2