nodes (and maybe
multiple number of vnodes per node) at extreme scales like that to get a
sense of what kind of overhead vnodes adds to the current gossip
implementation at scale.
Regarding existing bugs that you might usefully reproduce, I'll leave
that to others.
Thanks.
-Tupshin
On Fri, A
To clarify, I'm +1ing the creation of a stable 2.2 branch, prior to
8099, in order to not block certain key features, as mentioned. Neutral
on any additional nuances.
-Tupshin
On Sun, May 10, 2015, at 08:05 AM, tups...@tupshin.com wrote:
> +1
>
> On Sat, May 9, 2015, at 06:38 PM,
+1
On Sat, May 9, 2015, at 06:38 PM, Jonathan Ellis wrote:
> *With 8099 still weeks from being code complete, and even longer from
> being
> stable, I’m starting to think we should decouple everything that’s
> already
> done in trunk from 8099. That is, ship 2.2 ASAP with - Windows support-
> UDF
Hi Jatin,
I believe there is a lot of interest in developing RAMP transactions for
Cassandra, but no concrete activity yet.
https://issues.apache.org/jira/browse/CASSANDRA-7056
-Tupshin
On Mon, Feb 9, 2015, at 11:30 PM, Jatin Ganhotra wrote:
> Hi,
>
> Please forgive me if this is not
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
&g
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 T
+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
hrift jar, and rebuilding interface/thrift/gen-java.
Thoughts?
-Tupshin
On 6/18/2010 12:12 PM, Eric Evans wrote:
If there aren't any objections, I'd like to target the end of this month
for the next point release, 0.6.3.
If you have any show-stoppers that you feel should absolutely m
10 matches
Mail list logo
