cascading-cassandra
cascading-cassandra copied to clipboard
Test failing with cassandra 2.0.2 +
cascalog queries are failing with cassandra-all 2.0.2 and 2.0.3 dependency.
Also Is there a particular reason why the project is compiled with a 1.2.11 release of cassandra? With newer versions i am not able to build the project itself.
Also for cql3 scheme i am not able to get queries working with anything above and including 2.0.0.
We've made changes for compat with 2.0.2 in a branch. Problem is with some internal incompatibilities, I'll merge it to master shortly.
Will keep it for bookkeeping
I dont know enough travis, but would it be possible to have builds and tests against multiple version of cassandra deps?
It'd be more about leiningen, I'd say, since we're using embedded cassandra for testing...
I think it'll be a bit too complex, but actually not required, too. I can't think of any feature that's used by cassandra-hadoop that's not available in 1.2
I am new to cassandra but i have this perception that there are big changes in cassandra from versions to versions. I am not sure what cassandra-hadoop is, or how it is relevant to this project? But I was talking about having builds against multiple versions of cassandra-all dependency.
Its also true that builds would be more about lein. We can actually have multiple lein profiles with different versions of cassandra-all dep and have travis builds with "with-profile". Does that makes sense?
partially, yes. Thing is that we're using a forked version of Cassandra in order to provide a working hadoop integration (current version is broken for 2.x hadoop).
So whenever we include cassandra-all dependency, we load different versions of classes that we have overriden.
But we can try, sure.
As far as I can tell, CQL / Thrift interfaces didn't change much. They've certainly added a couple of features but they're orthogonal to what we're testing here, i'd say. I've tested it against 1.2.11 and 2.0.3, works just fine.
Great! Looking forward for the patch then.
Thanks
we can probably stop using a forked version of cassandra now... my fix was accepted into c_1.2 branch, and i think is in 1.2._ releases >= 1.2.10
i 'll check when i'm back behind a keyboard in a few days
On 27 Dec 2013, at 11:38, Alex P [email protected] wrote:
partially, yes. Thing is that we're using a forked version of Cassandra in order to provide a working hadoop integration (current version is broken for 2.x hadoop).
So whenever we include cassandra-all dependency, we load different versions of classes that we have overriden.
But we can try, sure.
As far as I can tell, CQL / Thrift interfaces didn't change much. They've certainly added a couple of features but they're orthogonal to what we're testing here, i'd say. I've tested it against 1.2.11 and 2.0.3, works just fine.
— Reply to this email directly or view it on GitHubhttps://github.com/ifesdjeen/cascading-cassandra/issues/17#issuecomment-31257454 .
Problem is with the hadoop 2.x, it doesn't work with cassandra without patches,...