RE: Change authorization from AllowAllAuthorizer to CassandraAuthorizer

Which Cassandra version? Most of my authentication-from-non-authentication experience is from Cassandra 1.1 – 2.0. After that, I just enable from the beginning. Sean Durity – Lead Cassandra Admin Big DATA Team MTC 2250 For support, create a JIRA

Re: How to remove 'compact storage' attribute?

Hi, You can't yet, see https://issues.apache.org/jira/browse/CASSANDRA-10857Note that secondary indexes don't scale. Be aware of their limitations.If you want to change the data model of a CF, a Spark job can do the trick. Best, Romain Le Mardi 7 juin 2016 10h51, "Lu, Boying" a écrit :

Re: Nodetool repair inconsistencies

Hi Jason, It's difficult for the community to help you if you don't share the error ;-)What the logs said when you ran a major compaction? (i.e. the first error you encountered) Best, Romain Le Mercredi 8 juin 2016 3h34, Jason Kania a écrit : I am running a 3 node cluster of 3.0.6 inst

Re: Lightweight Transactions during datacenter outage

Tyler, Thank you, it's working now: self.query['online'] = SimpleStatement("UPDATE table USING ttl %s SET l = True WHERE k2 = %s IF l = False;", consistency_level=ConsistencyLevel.LOCAL_QUORUM, serial_consistency_level=ConsistencyLevel.LOCAL_SERIAL) Would you know why the driver doesn't automati

Re: Change authorization from AllowAllAuthorizer to CassandraAuthorizer

Hi, Just a feedback from my scenario, it all went well, no downtime. In my case, I had authentication enabled from the beginning, just needed to change the authorizer. Felipe Esteves Tecnologia felipe.este...@b2wdigital.com Tel.: (21) 3504-7162 ramal 57162 Skype: felipe2esteves 2016-06-08 9

Re: Nodetool repair inconsistencies

Hi Romain, The problem is that there is no error to share. I am focusing on the inconsistency that when I run nodetool repair, get no errors and yet the content in the same directory on the different nodes is vastly different. This lack of an error is nature of my question, not the nodetool comp

Re: Lightweight Transactions during datacenter outage

> Would you know why the driver doesn't automatically change to LOCAL_SERIAL > during a DC outage ? I would say because *you* decide, not the driver ;-) This kind of fallback could be achieved with a custom downgrading policy (DowngradingConsistencyRetryPolicy [*] doesn't handle ConsistencyLevel

Re: Nodetool repair inconsistencies

Hi Jason - Did you run a major compaction after the repair completed? Do you have other reasons besides the number/size of sstables to believe all nodes don't have a copy of the current data at the end of the repair operation? Thanks, Paul On Wed, Jun 8, 2016 at 8:12 AM, Jason Kania wrote: > H

Re: Consistency level ONE and using withLocalDC

Hi George, Would that be correct? I think it is actually quite the opposite :-). It is very well explained here: https://docs.datastax.com/en/drivers/java/2.0/com/datastax/driver/core/policies/DCAwareRoundRobinPolicy.Builder.html#withUsedHostsPerRemoteDc-int- Connection is opened to the X node

Re: Nodetool repair inconsistencies

Hi Paul, I have tried running 'nodetool compact' and the situation remains the same after I deleted the files that caused 'nodetool compact' to generate an exception in the first place. My concern is that if I delete some sstable sets from a directory or even if I completely eliminate the sstabl

Re: Unable to use native library in C* trigger

Thank you very much! I am able to use the library now after adding it to the whitelist. Brian From: Ben Slater mailto:ben.sla...@instaclustr.com>> Reply-To: "user@cassandra.apache.org" mailto:user@cassandra.apache.org>> Date: Tuesday, June 7, 2016 at 4:30 PM To

Re: Change authorization from AllowAllAuthorizer to CassandraAuthorizer

C* version I am using is 2.1.13 Cluster 1 - Single DC Cluster 2 - Multi DC On Wed, Jun 8, 2016 at 7:01 AM, Felipe Esteves < felipe.este...@b2wdigital.com> wrote: > Hi, > > Just a feedback from my scenario, it all went well, no downtime. In my > case, I had authentication enabled from the beginn

Interesting use case

We have a use case where we are storing event data for a given system and only want to retain the last N values. Storing extra values for some time, as long as it isn’t too long, is fine but never less than N. We can't use TTLs to delete the data because we can't be sure how frequently events wil

Re: Interesting use case

I would say it's probably due to a significantly larger number of partitions when using the overwrite method - but really you should be seeing similar performance unless one of the schemas ends up generating a lot more disk IO. If you're planning to read the last N values for an event at the same t

RE: Interesting use case

Why do you think the amount of partitions is different in these tables? The partition key is the same (system_name and event_name). The number of rows per partition is different. From: kurt Greaves [mailto:k...@instaclustr.com] Sent: Thursday, June 09, 2016 7:52 AM To: user@cassandra.apache.or