+1
On Sun, Sep 7, 2014 at 9:23 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
We have no outstanding tickets open and tests are in the green, so I
propose
the following artifacts for release as 2.1.0.
sha1: c6a2c65a75adea9a62896269da98dd036c8e57f3
Git:
+1
--
AY
On Sunday, September 7, 2014 at 10:24 AM, Brandon Williams wrote:
+1
On Sun, Sep 7, 2014 at 9:23 AM, Sylvain Lebresne sylv...@datastax.com
(mailto:sylv...@datastax.com)
wrote:
We have no outstanding tickets open and tests are in the green, so I
propose
the following
+1
On Sun, Sep 7, 2014 at 9:23 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
We have no outstanding tickets open and tests are in the green, so I
propose
the following artifacts for release as 2.1.0.
sha1: c6a2c65a75adea9a62896269da98dd036c8e57f3
Git:
+1
On Sun, Sep 7, 2014 at 10:23 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
We have no outstanding tickets open and tests are in the green, so I
propose
the following artifacts for release as 2.1.0.
sha1: c6a2c65a75adea9a62896269da98dd036c8e57f3
Git:
Greetings,
This heuristic helps us eliminate unnecessary I/O in certain workloads and
datasets, by often many orders of magnitude. This is description of the
problems we faced and how we dealt with it — I am pretty certain this can be
easily implemented on C*, albeit will likely require a new
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 krum...@gmail.com wrote:
1. create a class that extends AbstractCompactionStrategy (i would keep it
+1
On Sun, Sep 7, 2014 at 9:23 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
We have no outstanding tickets open and tests are in the green, so I
propose
the following artifacts for release as 2.1.0.
sha1: c6a2c65a75adea9a62896269da98dd036c8e57f3
Git:
Hi Mark,
This specific heuristic is unlikely to be applied, as (if I've understood
it correctly) it has a very narrow window of utility to only those updates
that hit *exactly* the same clustering columns (cql rows) *and *data
columns, and is not trivial to maintain (either cpu- or memory-wise).
Hi Benedict,
On Sep 8, 2014, at 4:01 AM, Benedict Elliott Smith
belliottsm...@datastax.com wrote:
Hi Mark,
This specific heuristic is unlikely to be applied, as (if I've understood
it correctly) it has a very narrow window of utility to only those updates
that hit *exactly* the same
+1
On Sun, Sep 7, 2014 at 4:17 PM, Josh McKenzie josh.mcken...@datastax.com
wrote:
+1
On Sun, Sep 7, 2014 at 9:23 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
We have no outstanding tickets open and tests are in the green, so I
propose
the following artifacts for release as 2.1.0.
10 matches
Mail list logo