Re:Question about compaction strategy changes

hi Edwards, when changibg gc_grace_second, no compaction willbbe triggered. regards, jasonstack Sent from my Mi phoneOn Seth Edwards , Oct 22, 2016 11:37 AM wrote:Hello! We're using TWCS and we notice that if we make changes to the options to the window unit or size, it

Question about compaction strategy changes

Hello! We're using TWCS and we notice that if we make changes to the options to the window unit or size, it seems to implicitly start recompacting all sstables. Is this indeed the case and more importantly, does the same happen if we were to adjust the gr_grace_seconds for this table? Thanks!

Re: Cannot restrict clustering columns by IN relations when a collection is selected by the query

So the commit on this restriction dates back to 2.2.0 (CASSANDRA-7981). Maybe Benjamin Lerer can shed some light on it. On Fri, Oct 21, 2016 at 11:05 PM, Jeff Carpenter < jeff.carpen...@choicehotels.com> wrote: > Hello > > Consider the following schema: > > CREATE TABLE rates_by_code ( >

Cannot restrict clustering columns by IN relations when a collection is selected by the query

Hello Consider the following schema: CREATE TABLE rates_by_code ( hotel_id text, rate_code text, rates set, description text, PRIMARY KEY ((hotel_id), rate_code) ); When executing the query: select rates from rates_by_code where hotel_id='AZ123' and rate_code IN ('ABC', 'DEF',

Re: Does anyone store larger values in Cassandra E.g. 500 KB?

1. usually before storing object, serialization is needed, so we can know the size. 2. add "chunk id" as last clustering key. Vikas Jaiman 于2016年10月21日周五 下午11:46写道： > Thanks for your answer but I am just curious about: > > i)How do you identify the size of the object

Re: Does anyone store larger values in Cassandra E.g. 500 KB?

Thanks for your answer but I am just curious about: i)How do you identify the size of the object which you are going to chunk? ii) While reading or updating how it is going to read all those chunks? Vikas On Thu, Oct 20, 2016 at 9:25 PM, Justin Cameron wrote: > You

Re: Cluster Maintenance Mishap

Thanks. Unfortunately, we lost our system logs during all of this (had normal logs, but not system) due to an unrelated issue :/ Anyhow, as far as I can tell, we're doing okay. On Thu, Oct 20, 2016 at 11:18 PM, Jeremiah D Jordan < jeremiah.jor...@gmail.com> wrote: > The easiest way to figure

Re: Cluster Maintenance Mishap

It mostly seems so. The thing that bugs me is that some things acted like they weren't joining as a normal new node. For example, I forgot to mention until I read your comment, that the instances showed as UN (up, normal) instead of UJ (up, joining) while they were apparently bootstrapping.

Re: Is SASI index in Cassandra efficient for high cardinality columns?

Why Secondary index cannot be broken down into token ranges like primary index at least for exact matches? That way dont need to scan the whole cluster atleast for exact matches. I understand if it is a substring search then there will 2^n substrings which equates to 2^n hashes/tokens which can be

Re: failure node rejoin

Just to confirm, are you saying: a) after operation 2, you select all and get 1000 rows b) after operation 3 (which only does updates and read) you select and only get 953 rows? If so, that would be very unexpected. If you run your tests without killing nodes do you get the expected (1,000) rows?

Re: failure node rejoin

> Are you certain your tests don’t generate any overlapping inserts (by PK)? Yes. The operation 2) also checks the number of rows just after all insertions. On Fri, Oct 21, 2016 at 2:51 PM, Ben Slater wrote: > OK. Are you certain your tests don’t generate any