It seems like there are many people in this thread that would rather we not
make a “grouping” CEP for these ideas, but rather consider each one
individually. I will close out this CEP thread then, and discussions can
continue on individual tickets.
I think we got some nice discussion on this t
> On Oct 25, 2021, at 1:22 PM, Jeremiah D Jordan wrote:
>
> The currently proposed changes in CEP-18 should all include improved test
> coverage of the modules in question. We have been developing them all with a
> requirement that all changes have at least %80 code coverage from sonar cloud
heavy pruning.
From: Stefan Miklosovic
Date: Tuesday, 26 October 2021 at 20:40
To: dev@cassandra.apache.org
Subject: Re: [DISCUSS] CEP-18: Improving Modularity
I am all for good extensibility / interfaces and so on, however I am
afraid that this might actually break a lot of things if enough
attent
ers’ opinions about this.
>
> The only sub-proposal I’m particularly unsure about is 17059, which doesn’t
> seem to increase modularity at all. It looks to be a kind of plugin hook, and
> IMO should definitely be addressed separately. Perhaps a simple DISCUSS
> thread and its Jira wil
> > at
> > > least questions as to how they work. As we have a backlog of several
> > fairly
> > > substantial CEPs lined up, we are trying to be very mindful of the
> > > bandwidth of the developers on this list. For example, last week Jacek
> > also
> >
assandra.apache.org
Subject: Re: [DISCUSS] CEP-18: Improving Modularity
>
> To me having some defined interfaces for interacting with different
> sections of the code is a huge boon for improving developer productivity
> going forward in the project. Every place where we can reduce the a
h I think is a primarily
> to support an external dependency but we expect this area of the codebase
> to be significantly revised over the coming months.
> >
> >
> > From: Henrik Ingo henrik.i...@datastax.com>>
> > Date: Monday, 25 October 2021 at 14:52
> &
Henrik Ingo mailto:henrik.i...@datastax.com>>
> Date: Monday, 25 October 2021 at 14:52
> To: dev@cassandra.apache.org <mailto:dev@cassandra.apache.org>
> mailto:dev@cassandra.apache.org>>
> Subject: Re: [DISCUSS] CEP-18: Improving Modularity
> Hi Benedict
ficantly revised over the coming months.
>
>
> From: Henrik Ingo
> Date: Monday, 25 October 2021 at 14:52
> To: dev@cassandra.apache.org
> Subject: Re: [DISCUSS] CEP-18: Improving Modularity
> Hi Benedict
>
> This CEP is a bundle of APIs arising out of our recent work
think it would be preferable to tie them to
> those features - perhaps with their own CEP?
>
>
> From: Jeremiah Jordan
> Date: Friday, 22 October 2021 at 16:24
> To: Cassandra DEV
> Subject: [DISCUSS] CEP-18: Improving Modularity
> Hi All,
> As has been seen with the work alre
them to
> those features - perhaps with their own CEP?
>
>
> From: Jeremiah Jordan
> Date: Friday, 22 October 2021 at 16:24
> To: Cassandra DEV
> Subject: [DISCUSS] CEP-18: Improving Modularity
> Hi All,
> As has been seen with the work already started in CEP-10, increasin
think it would be preferable to tie them to
> those features - perhaps with their own CEP?
>
>
> From: Jeremiah Jordan
> Date: Friday, 22 October 2021 at 16:24
> To: Cassandra DEV
> Subject: [DISCUSS] CEP-18: Improving Modularity
> Hi All,
> As has been seen with the work alre
work is primarily intended to enable certain
features, I personally think it would be preferable to tie them to those
features - perhaps with their own CEP?
From: Jeremiah Jordan
Date: Friday, 22 October 2021 at 16:24
To: Cassandra DEV
Subject: [DISCUSS] CEP-18: Improving Modularity
Hi All,
As
Hi All,
As has been seen with the work already started in CEP-10, increasing the
modularity of our subsystems can improve their testability, and also the
ability to try new implementations without breaking things.
Our team has been working on doing this and CEP-18 has been created to
propose addin
14 matches
Mail list logo
