In addition to what Markus said, take a look at the latest patch in
https://issues.apache.org/jira/browse/CASSANDRA-6602 for a relevant
example.
-Tupshin
On Sep 4, 2014 2:28 PM, "Marcus Eriksson" wrote:
> 1. create a class that extends AbstractCompactionStrategy (i would keep it
> in-tree while
Hi David,
Check out the ongoing discussion in
https://issues.apache.org/jira/browse/CASSANDRA-6704 as well as some
related tickets linked to from that one.
No consensus at this point, but I'm personally hoping to see something
along the general lines of Hive's UDFs.
-Tupshin
On Thu, Feb 27, 20
+1
On Feb 6, 2013 5:22 PM, "Jonathan Ellis" wrote:
> Java 6 EOL is this month. Java 7 will be two years old when C* 2.0
> comes out (July). Anecdotally, a bunch of people are running C* on
> Java7 with no issues, except for the Snappy-on-OS-X problem (which
> will be moot if LZ4 becomes our def
As long as network compatibility is in place, it is possible to
incrementally upgrade a cluster by restricting thrift clients to only talk
to the 0.6 nodes until half the cluster is upgraded and then modify them to
talk to the 0.7 nodes. If networking compatibility breaks, there is no way
to avoid
On 6/18/2010 1:24 PM, Eric Evans wrote:
On Fri, 2010-06-18 at 12:25 -0700, Tupshin Harper wrote:
I would like to nominate #475 for inclusion in 0.6.3. It would require
picking a stable recent snapshot of the thrift libs, replacing the
existing libthrift jar, and rebuilding interface/thrift
Contrary to my expectations and Jonathan's, Cassandra rebuilds cleanly
against the latest thrift source (and any recent snapshot), with no code
changes. This is important because it includes the patches for
https://issues.apache.org/jira/browse/THRIFT-601
which, in turn, causes
https://issues.ap
