On Fri, Dec 11, 2015 at 8:34 AM, DuyHai Doan wrote:
> The new UDF (User Defined Function) and UDA (User Defined Aggregate)
> introduced since Cassandra 2.2 is the feature to closest HBase co-processor.
>
Aren't "Prototype Triggers" (which probably no one should use) closer?
http://www.datastax.
Anuj, Jeff, thank you both,
Although harmless, sounds like it's time for an upgrade. The ticket
suggests that 2.0.17 is not affected.
Thank you guys!
On Fri, Dec 11, 2015 at 5:25 PM, Jeff Jirsa
wrote:
> Same bug also affects 2.0.16 -
> https://issues.apache.org/jira/browse/CASSANDRA-9662
>
> F
Same bug also affects 2.0.16 -
https://issues.apache.org/jira/browse/CASSANDRA-9662
From: Jeff Jirsa
Reply-To:
Date: Friday, December 11, 2015 at 9:12 AM
To: "user@cassandra.apache.org"
Subject: Re: Thousands of pending compactions using STCS
There were a few buggy versions in 2.1 (2.1.7,
Sorry I missed the version in your mail..you are on 2.0.16..so it cant be
coldness issue..
Anuj
Sent from Yahoo Mail on Android
From:"Anuj Wadehra"
Date:Fri, 11 Dec, 2015 at 10:48 pm
Subject:Re: Thousands of pending compactions using STCS
There was a JIRA that cold sstables are not compacte
There was a JIRA that cold sstables are not compacted leading to thousands of
sstables. Issue got fixed in 2.0.4. Which version of Cassandra are you using?
Anuj
Sent from Yahoo Mail on Android
From:"Jeff Jirsa"
Date:Fri, 11 Dec, 2015 at 10:42 pm
Subject:Re: Thousands of pending compactions us
On Fri, Dec 11, 2015 at 1:59 AM, Janne Jalkanen
wrote:
>
> So there is no reason why you would ever want to run 3.1 then?
>
Probably not.
> Why was it released?
>
For consistency. It's the first release in the new tick-tock release
scheme. Skipping that would have been a bit strange (altho
There were a few buggy versions in 2.1 (2.1.7, 2.1.8, I believe) that showed
this behavior. The number of pending compactions was artificially high, and not
meaningful. As long as they number of –Data.db sstables remains normal,
compaction is keeping up and you’re fine.
- Jeff
From: Vasileios
The new UDF (User Defined Function) and UDA (User Defined Aggregate)
introduced since Cassandra 2.2 is the feature to closest HBase co-processor.
1. They are real time, in the sense that they are applied right away on the
fly after fetching data from C*
2. The computation is done on the coordinato
Inconsistent reads are most often the result of inconsistent data between
nodes. Inconsistent data during tests like this is quite often the result
of having loaded data fast enough that you dropped mutations (writing even
at quorum means that you could still be dropping data on some nodes and not
Hi all,
Now we insert 1 billion rows or more of datas into C*, and then we use
select command to export datas into local files. but each time when we use such
SELECT command : SELECT * from table where id = xxx and id2 > value1 and id2 <=
value2; to query the datas in C* and then export the
Thanks for this clarification, however...
> So, for the 3.x line:
> If you absolutely must have the most stable version of C* and don't care at
> all about the new features introduced in even versions of 3.x, you want the
> 3.0.N release.
So there is no reason why you would ever want to run 3.1
11 matches
Mail list logo
