Hi guys,
I saw your message on IRC Jason, Kurt forwarded it to me. Thanks for the
heads up!
3.11 presently doesn't build, I think it may have been due to an accidental
merge gone bad. The original JIRA
https://issues.apache.org/jira/browse/CASSANDRA-13698 has been updated with
a patch and the
; On Mon, Jun 4, 2018 at 6:02 PM Lerh Chuan Low
> wrote:
>
> > Hi Eric,
> >
> > I think it has something to do with the same reason it is disabled in
> DTCS:
> > https://issues.apache.org/jira/browse/CASSANDRA-9234 can shed more
> light.
> >
> >
>
Hi Eric,
I think it has something to do with the same reason it is disabled in DTCS:
https://issues.apache.org/jira/browse/CASSANDRA-9234 can shed more light.
On 5 June 2018 at 09:02, Eric Stevens wrote:
> I'm trying to understand the reasoning behind this stanza in Time Windowed
>
For reasons others have mentioned (nightmare to continuously update branch
and resolve merge conflicts, existing patches/big features..) it will be a
nightmare. It seems like in software projects (just basing it off personal
experience) people typically refactor if a ticket they are working on
Dear all,
Just wondering if anyone has any available capacity to have a look through
https://issues.apache.org/jira/browse/CASSANDRA-8460 and give their
thoughts on the initial patch I have?
Namely the decisions on having archiving configurable from the YAML but
controlled from the Compaction
a hand with anything?
Lerh
On 18 May 2017 at 03:36, Ariel Weisberg <ar...@weisberg.ws> wrote:
> Hi,
>
> Thank you Blake, Lerh Chuan Low, Jason, and Kurt, and anyone else who
> volunteered.
>
> I'm going to look at repair_test.TestRepair which is not quite the same
> as rep
