Re: Re-importing Cassandra dependencies with Ant and IntelliJ 14.03

OK @all, I think I was finally able to fix the issue. I did this to fix it (in the top-level dir of my Cassandra install): nkelkar@nkelkar-laptop:~/cassandra$ *ant -v generate-idea-files* Is this documented somewhere (in the README.txt, etc.)? It is super useful for first-time Ant users like

Re: Re-importing Cassandra dependencies with Ant and IntelliJ 14.03

OK, I changed my branch to a much recent version (3.5) and I've been able to narrow the problem down to task* build-test* only. Specifically, when I trigger that task, I get the following error: *Compile failed; see the compiler error output for details.* This error points to the following

Re-importing Cassandra dependencies with Ant and IntelliJ 14.03

Hi all, I very recently forked the Cassandra code base as directed here: https://wiki.apache.org/cassandra/HowToContribute I then changed my language level to Java 8, and opened the project in IntelliJ. However, many of the dependencies (DataStax, Apache Commons, etc.) appear in *red* because

Re: com.datastax.driver.core.Connection "This should not happen and is likely a bug, please report."

Hi Thunder, This would be better sent to the Java mailing list https://groups.google.com/a/lists.datastax.com/forum/#!forum/java-driver-user. A quick search revealed https://datastax-oss.atlassian.net/browse/JAVA-603 which seem to match the Cassandra/DataStax community version but not the driver

Scenarios when a node can be missing writes

Hi, I'm trying to reason the possible scenarios when a node of a C* cluster is not getting the writes and the data needs some sort of anti-entropy (repair, read-repair, etc.). In what cases does the coordinator not realize that a write failed and doesn't replay the write from hinted handoff

Re: Transaction Support in Cassandra

That said, if you *really* want transactionality other than what's provided by batches, you should probably look into a more suitable solution. Using Cassandra exclusively with lightweight transactions at quorum writes will put serious load on it, and you probably won't achieve decent write

Re: disk space used vs nodetool status

Thanks Carlos, We didn't do any actions that would create a snapshot, and i couldn't find the command in 2.0.17, but i found the respective snapshot directories and they were created from more than a couple of months ago so, i it might be that i might have forgotten, its fine now, i have cleared

Re: Transaction Support in Cassandra

"So what will be the closest Alternative of Transaction in Cassandra" --> A batch of mutations with LightweightTransaction for a single partition or simple LightweightTransaction On Tue, Mar 22, 2016 at 11:04 AM, Bhupendra Baraiya < bhupendra.bara...@continuum.net> wrote: > Ok so we will not get

RE: Transaction Support in Cassandra

Ok so we will not get what they had developed So what will be the closest Alternative of Transaction in Cassandra Thanks and regards, Bhupendra Baraiya Continuum Managed Services, LLC. p: 902-933-0019 e: bhupendra.bara...@continuum.net w: continuum.net

Re: disk space used vs nodetool status

I'd say you have snapshots holding disk space. Check it with nodetool listsnapshots. A snapshot is automatically taken on destructive actions (drop, truncate...) and is basically a hard link to the involved SSTables, so it's not considered as data load from Cassandra but it is effectively using

Re: Transaction Support in Cassandra

First Ok.ru support for acid transactions is using a complete FORK of Apache Cassandra so people using it need to maintain the fork themselves. Second, as far as I know, they don't intend to publish the source code so it's not really available in the public space either. The reason is that their

Transaction Support in Cassandra

HI , We are currently thinking of moving from Sql to Cassandra but our major worry here is we have a system which required concurrent 200 connection at time and they do the updates and insert and delete which requires Transaction support When I searched o Google about these what I got is