For the Parisian out there, we're having the 2nd installment of the
Paris Cassandra Meetup next Thursday (October 11).
This time, we'll have Matt Dennis coming all the way from Austin to
talk about "Apache Cassandra data model differences compared to
RDBMS".
You don't want to miss that so go see t
Try making user_name a primary key in combination with some other unique column
and see if results are improving.
-Rishabh
From: Vivek Mishra [mailto:mishra.v...@gmail.com]
Sent: Friday, October 05, 2012 2:35 PM
To: user@cassandra.apache.org
Subject: Query over secondary indexes
I have a column f
Thanks Rishabh. But i want to search over duplicate columns only.
-Vivek
On Fri, Oct 5, 2012 at 2:45 PM, Rishabh Agrawal <
rishabh.agra...@impetus.co.in> wrote:
> Try making *user_name* a primary key in combination with some other
> unique column and see if results are improving.
>
> -Rishabh
>
Hi there,
Is anyone out here familiar with the Simba Cassandra ODBC?
http://www.simba.com/Apache-Cassandra-ODBC-Driver-SQL-Connector.htm
We're thinking of some kind of Hadoop > Hive > Cassandra > Tableau
(visualization software) ETL process. But in that case, an ODBC driver on
top of C* is requir
When restoring a backup for the entire cluster my understanding is that
you must shutdown the entire cluster and then restore the backup and
then start up all nodes again.
http://www.datastax.com/docs/1.0/operations/backup_restore
But how should I handle hinted handoffs (Hints CF). Since they're
I guess that the other nodes still gossips about the removed node. The
node isn't removed from gossiper in the cluster until some amount of
time have elapsed. My guess is that you haven't changed the cluster_name
property in the cassandra.yaml on the removed node.
Xu, Zaili skrev 2012-09-28
What if gc_grace_seconds is pretty low, say 2 mins, what happens with
nodetool repair ?
That wiki page below points at a bug that has been fixed long ago. Is
it still an issue if you don't run a repair within gc_grace_seconds ?
On 2012-01-09 10:02:49 +, aaron morton said:
Nah, thats old
Hello,
We are planning to upgrade from version 1.0.7 to the 1.1 branch. Which is
the stable version that people are using? I see the latest release is 1.1.5
but maybe it's not fully wise to use this. Is 1.1.4 the one to use?
Cheers,
Alex
In 1.1.5 file descriptor leak was fixed. In my case it was critical.
Nodes went down every several days. But not everyone had this problem.
Thank you,
Andrey
On Fri, Oct 5, 2012 at 7:42 AM, Alexandru Sicoe wrote:
> Hello,
> We are planning to upgrade from version 1.0.7 to the 1.1 branch. Whic
We've been using 1.1.5 for a few weeks now and it's been stable for our
uses. Also, make sure you upgrade to a more recent version of 1.0 branch
before going to 1.1. Version 1.0.7 was released before 1.1 and there are
upgrade-path fixed applied to 1.0 after that. Our upgrade path was 1.0.9
-> 1.
i believe the system keyspace keeps track of the cluster topology.
even though you changed info in yaml, the system keyspace still knows
about the other nodes. remove the system keyspace files from data dir
and try again
On Fri, Oct 5, 2012 at 4:47 AM, Fredrik
wrote:
> I guess that the other nod
I am using CQL 3 and trying to execute the following,
UPDATE CHANGELOGLOCK SET LOCKED = 'true', LOCKEDBY = '10.11.8.242
(10.11.8.242)', LOCKGRANTED = '2012-10-05 16:58:01' WHERE ID = 1 AND LOCKED
= 'false';
It gives me the error, Bad Request: PRIMARY KEY part locked found in SET
part. The primar
I've recently added compaction rate (in bytes / second) to my monitors for
cassandra and am seeing some odd values. I wasn't expecting the values for
TotalBytesCompacted to sometimes decrease from one reading to the next. It
seems that the value should be monotonically increasing while a server i
13 matches
Mail list logo
