Re: Left Cassandra mailing list

2016-08-01 Thread Andrey Ilinykh
To remove your address from the list, send a message to: On Mon, Aug 1, 2016 at 11:29 PM, Mohammad Kermani <98kerm...@gmail.com> wrote: > How can I leave Cassandra mailing list? > > I get some emails every day and currently I do not have time for it > >

Re: Left Cassandra mailing list

2016-08-01 Thread Julien Anguenot
Hey Mohammad, Just send a message to user-unsubscr...@cassandra.apache.org using the email address you subscribed with and you should be good to go. See header of page: http://mail-archives.apache.org/mod_mbox/cassandra-user/ J. -- Julien A

Re: duplicate values for primary key

2016-08-01 Thread Julien Anguenot
Hey Oskar, I would comment and add all possible information to that Jira issue… J. -- Julien Anguenot (@anguenot) > On Aug 2, 2016, at 8:36 AM, Oskar Kjellin wrote: > > Hi, > > Ran into the same issue when going to 3.5. Completely killed our cluster. > Only way was to restore a backup.

Re: duplicate values for primary key

2016-08-01 Thread Oskar Kjellin
Hi, Ran into the same issue when going to 3.5. Completely killed our cluster. Only way was to restore a backup. /Oskar > On 2 aug. 2016, at 07:54, Julien Anguenot wrote: > > Hey Jesse, > > You might wanna check and comment against that issue: > > https://issues.apache.org/jira/browse/CAS

Left Cassandra mailing list

2016-08-01 Thread Mohammad Kermani
How can I leave Cassandra mailing list? I get some emails every day and currently I do not have time for it

Re: duplicate values for primary key

2016-08-01 Thread Julien Anguenot
Hey Jesse, You might wanna check and comment against that issue: https://issues.apache.org/jira/browse/CASSANDRA-11887 J. -- Julien Anguenot (@anguenot) > On Aug 2, 2016, at 3:16 AM, Jesse Hodges wrote: > > Hi, I've got a bit of a conundrum. Recently I upgraded from 2.2.3 to 3.7.0 > (

duplicate values for primary key

2016-08-01 Thread Jesse Hodges
Hi, I've got a bit of a conundrum. Recently I upgraded from 2.2.3 to 3.7.0 (ddc distribution). Following the upgrade (though this condition may have existed prior to upgrade).. I have a table with a simple partition key and multiple clustering keys, and I have duplicates of many of the primary key