Does range query ignore purgable tombstone (which crossed grace period) in
some cases?
On Tue, Jun 11, 2019, 2:56 PM Laxmikant Upadhyay
wrote:
> In a 3 node cassandra 2.1.16 cluster where, one node has old mutation and
> two nodes have evict-able (crossed gc grace period) tombstone produced by
>
Hi All,
I would like to propose a new feature in the Cassandra row cache.
The proposition is for the use-case when you have a table where most of the
read access is done on a few columns and the table has millions of rows.
To improve cache memory size I have 2 possible improvement propositions:
Thanks for starting this discussion, Sumanth! Added a round of comments as well.
Summarizing my non-binding feedback: I feel that many of the items under
"Alpha" and "Beta" should be achieved prior to the release of an alpha,
especially those related to correctness/safety, scope lock, feature
c
Had a few more points of feedback for you Sumanth; trying to get some
clarity on how the PMC might function w/relation to the various votes and
definitions.
Thanks for the integration and continued effort on this - it's looking good!
On Tue, Jun 11, 2019 at 9:45 AM Sumanth Pasupuleti <
sumanth.pa
Thanks for the feedback on the product stages/ release life cycle document.
I have incorporated the suggestions and looking for any additional feedback
folks may have.
https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#
Thanks,
Sumanth
On Tue, May 28, 2019 at 10:
Hi All,
Just FYI
I did a Java 8 build (dist - to be more spcific, that involves $ ant
artifacts) from 4.0 trunk (after git pull) on Sunday morning (so 9th of
June) - there were no issues for me
I did it on both Windows and Linux (Debian) machines
Maybe there were commits since then.. I have n
> On 11 Jun 2019, at 10:04, Tommy Stendahl wrote:
>
> Hi,
>
> I can't find a way to build 4.0 artifacts so I can run Cassandra using Java8.
> Building the artifacts ("ant artifacts" or "ant mvn-install") requires
> building with Java11 but since CASSANDRA-15108 the result is not Java8
> co
No, this is not intentional. At the very least for 4.0 we are going to keep
compatibility with Java 8.
> On 11 Jun 2019, at 10:04, Tommy Stendahl wrote:
>
> Hi,
>
> I can't find a way to build 4.0 artifacts so I can run Cassandra using Java8.
> Building the artifacts ("ant artifacts" or "ant
Hi,
I can't find a way to build 4.0 artifacts so I can run Cassandra using Java8.
Building the artifacts ("ant artifacts" or "ant mvn-install") requires building
with Java11 but since CASSANDRA-15108 the result is not Java8 compatible
anymore, is this intentional or was this done by mistake?
I
