Hi Thanks for the response.
For that use case, the counter works fine. I'll change it.
But for some others use cases what I need to do is to obtain the "full
list" of users :
cqlsh:usmc> select userid from userpixel where trackid = 'ab1' and advid =
'adb1' and country = 'AR' and region = 'C' li
I haven't used this scala driver, but may possibly explore soon.
https://github.com/websudosuk/phantom
https://websudosuk.github.io/phantom/
Mentioned at at:
http://planetcassandra.org/client-drivers-tools/#Scala
http://www.datastax.com/download#dl-community-drivers
On Mon, Sep 1, 2014 at 10:
Using query tracing, as many have recommended here, will tell you where the
query is spending it's time. If there's a bottleneck somewhere, you'll see
it there.
On Tue, Sep 2, 2014 at 6:57 AM, eduardo.cusa <
eduardo.c...@usmediaconsulting.com> wrote:
> Hi Thanks for the response.
>
> For that
On Fri, Aug 29, 2014 at 7:09 PM, Donald Smith <
donald.sm...@audiencescience.com> wrote:
> But the node is a seed node and cassandra won't bootstrap seed nodes.
> Perhaps removing that node's address from the seeds list on the other nodes
> (and on that node) will be sufficient. That's what Repla
Hi,
Cassandra setup:
* 2 nodes on EC2, m1.large
* Cassandra version 2.0.10
One node died over the weekend, and I couldn't revive it. I deleted it with
nodetool removenode, and added a new node with a copy of the cassandra.yaml
config with the ip addresses changed.
Once reconfigured and starte
Hello Bram
You're probably running into this :
https://issues.apache.org/jira/browse/CASSANDRA-4417
It's marked as won't fix because it is related to the current counter
design. Fortunately C* 2.1 will fix this.
Worth reading :
www.datastax.com/dev/blog/whats-new-in-cassandra-2-1-a-better-implem
